How do I allow remote root login?

[Kegnut]

Im used to solaris with the /etc/default/login file. Can't seem to find it on Redat 7.2.

Thanks in advance,
Josh

 

[csimion]

Using Telnet you can't allow remote root login. Anyway, you can allow remote access as an usual user, then, using su - the user can change in the root user (by typing the root password).
Or, you can use a ssh client which allows any type of login.
Check your /etc/hosts.allow file for the hosts that are allowed to connect to you. Cristian

 

[mithrilhall]

You might want to leave behind Telnet and try SSH. Telnet isn't secure.

 

[garwain]

Actually, I did change something on an old server to allow root login via telnet. Don't remember what I did and I don't have a machine available that I'm willing to test on.

Best advice is DON'T DO IT. If you insist on having root log in directly, us SSH! The only reason I did it was because it was for a small company and the LAN had no internet access. All users a small program on their computer that would automatical log in via ftp, start up/ shut down some programs that needed to run as root and log out again. I would NEVER EVER do this on a machine with internet access! (or any situation where you can't trust EVERY person with access.)

 

[haneo]

Yes I agree with last postes DO NOT USE TELNET, as it is clear text message over the LAN !

Use SSH it is more secure and you can log with root (and with some modif you can log without typing the password every connection!)

But if you really want to telnet to linux PC as root see the file /etc/securetty

uncommante the line pts/0 pts/1 (the terminal that you will make accessible for root)

 

[Kegnut]

Thanks for all the input. I am trying to configure Veritas Netbackup server running on Solaris to back up one of my x86 Redhat Clients. When it attempts the backup, I get an error in regards to client connection refused. I should probably be writing in the netbackup area, but I figured it had something to do with this. If anyone else has run into this problem, please feel free to provide input. Thanks again for all your help and thanks in advance for any help here after.

J

 

[aixmurderer]

Rename the /etc/securetty to something else (e.g. securetty.old) and Bob is your uncle. IBM Certified Specialist - MQSeries
IBM Certified Specialist - AIX 5 pSeries System Administration

 

[Kegnut]

Appreciate the help, but I already have the securetty file renamed to securetty.org. As for Bob, I have no idea what you are talking about.

Any other ideas?
Thanks in advance,
J

 

[NOOB]

Add the lines

pts/0
pts/1
"
"
pts/6

Now you can login as root. But don't forget, it's not good !

Greetz

 

[NOOB]

Oh, i forget something. You must add the lines in /etc/securetty, of course !

Greetz

 

[Guest_imported]

I just put several machines up on Linux 2.4.7-10 (RedHat 7.2) Apparently Linux 7.x is supported in later releases of NetBackup. RH 7.x no longer utilizes inetd and uses xinetd instead. The configuration files for 7.x are different. For starters, on the linux client you need to make entries for pts/[0-11] in the /etc/securetty file or rename it so that root can rsh to it. If you are going to do a remote install, you need to edit ftpaccess and ftpusers files to allow a remote root user to set up the netbackup files. To install the files you need to do the following:

(It should be noted that anytime that you make changes to the /etc/services file on RH Linux 7.x you need to make the apropriate changes in the files in /etc/xinetd.d.)

on the Netbackup server as root execute:

# /usr/openv/netbackup/bin/install_client_files ftp client_name root

This transfers the files to the /tmp directory on the client

On the client as root execute:
# sh /tmp/bp/bin/client_config

Disregard the error message about the inetd.conf file

Then follow the procedures listed below:



Here's the Veritas technote on Linux clients:

Symptom:

NetBackup install client fails on Linux Redhat version 7.0. Linux Redhat
version 7.0 uses xinetd instead of inetd, along with a different file
structure. This version is not currently supported with NetBackup version
3.4.


Solution:

Linux Redhat vision 7.0 started using xinetd instead of inetd along with
different file structures. The same principles remain regarding inetd. The
file names have changed. The new file is called /etc/xinetd.conf, but this
is not the file that needs to be changed.
The correct process is to go to /etc/inetd.d, create three separate files
under this directory. They should be named bpcd, bpjava-msvc and vopied.

The three files should look like the following:


bpcd File

# description: BPCD server

service bpcd
{
disable = no
id = bpcd-stream
socket_type = stream
protocol = tcp
user = root
wait = no
server = /usr/openv/netbackup/bin/bpcd
}


bpjava-msvc File

# description: bpjava-msvc server

service bpjava-msvc
{
disable = no
id = bpjava-msvc-stream
socket_type = stream
protocol = tcp
user = root
wait = no
server = /usr/openv/netbackup/bin/bpjava-msvc
server_args = -transient
}


vopied File

# description: vopied server

service vopied
{
disable = no
id = vopied-stream
socket_type = stream
protocol = tcp
user = root
wait = no
server = /usr/openv/netbackup/bin/vopied
}

Have fun.....

 

[lgarner]

I'm trying to duplicate a print setup running on NetWare onto a Linux server. Basically, I need a Unix computer to send print jobs via LPR/LPD to the Linux server, where they will sit as individual files to be processed and published under the web site (same server).

This doesn't sound difficult, but I havent' been able to find too much documentation or examples on setting up a Linux print server.

Thanks.