Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: why to use su??

  1. #11
    Senior Member linuxcomando's Avatar
    Join Date
    Sep 2001
    Posts
    432
    Well first of all loging in as root over telnet isn't going to happen because telnet won't allow for root connections. Second of all telnet is all in plain text and not encrypted at all. Secure Shell on the other hand will allow for root login unless taken out of the ssh config file. But by default it will allow for root logons its alot safer then telnet because its encrypted at 128 bit (i could be wrong on this one) But i would still highly advise that you login in as root only if you need to else things seemed to get screwed up way to fast!
    I toor\'d YOU!

  2. #12
    Senior Member
    Join Date
    Oct 2001
    Posts
    677
    else things seemed to get screwed up way to fast!
    Agree with you on that one, linuxcommando.
    One Ring to rule them all, One Ring to find them.
    One Ring to bring them all and in the darkness bind them.
    (The Lord Of The Rings)
    http://www.bytekill.net

  3. #13
    uh linuxcommando, if you were such a commando you would know that root logins through telnet are possible.

  4. #14
    AntiOnline Senior Member souleman's Avatar
    Join Date
    Oct 2001
    Location
    Flint, MI
    Posts
    2,883
    You can change the /etc/securetty (spelling?) file to determine how root can log in. I disallow all root logins. I am the only admin, and I still require myself to su to root. If, by some chance, someone somehow gets the root password, they can't login directly, and the su would be noticeable. Especially since none of the users here know how to use *nix.

    Also, by forcing myself to su, it guarantees that I want to be root. I actually have to login twice to do something, so I force myself to think about what I am doing before I really screw something up.
    \"Ignorance is bliss....
    but only for your enemy\"
    -- souleman

  5. #15
    Member
    Join Date
    Aug 2001
    Posts
    69
    Originally posted here by celfie
    su provides cryptographically secured authentication. which protects from tcp hijacking and spoofing. and sniffing.
    If the remote user, connects to the terminal without SSH etc. su will not provide any protection against sniffers.

    Try, Fail but Do iT at last!
    ASA The ZeroTimeR
    The Turkish IT Documentation Project

  6. #16
    Senior Member
    Join Date
    Oct 2001
    Posts
    638
    You can change the /etc/securetty (spelling?) file to determine how root can log in. I disallow all root logins. I am the only admin, and I still require myself to su to root. If, by some chance, someone somehow gets the root password, they can't login directly, and the su would be noticeable. Especially since none of the users here know how to use *nix.
    souleman is right. Edit your /etc/securetty file (yes that is the correct spelling) and comment out all the ttyx lines to disallow root logins. For example:

    #tty1
    #tty2
    #tty3
    #tty4
    #tty5
    #tty6
    #tty7
    #tty8

    This mean no-one can login as root. They have to su -. FTP also has it's own files to stop logins from certain accounts. Use /etc/ftpusers to specify which accounts can't login to ftp (eg root, mail...). This has been deprecated for newer versions of linux/ftp. In this case use /etc/ftpaccess to specify the system accounts.
    OpenBSD - The proactively secure operating system.

  7. #17
    Senior Member
    Join Date
    Feb 2002
    Posts
    114
    Thanks for the help guy's i too was wonderin about remote root as i am a self connfessed [pong] newbie [/pong]
    [pong][gloworange]665[/gloworange] Next door to the [glowpurple]devil[/glowpurple][/pong]

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •