Date: Mon, 22 Jan 2001 14:01:16 -0700 From: Warner Losh <imp@harmony.village.org> To: Ted Sikora <tsikora@powerusersbbs.com> Cc: Juraj Lutter <otis@wilbury.sk>, "freebsd-stable@FreeBSD.ORG" <freebsd-stable@FreeBSD.ORG> Subject: Re: ssh login Message-ID: <200101222101.f0ML1G912295@harmony.village.org> In-Reply-To: Your message of "Mon, 22 Jan 2001 12:38:15 EST." <3A6C7007.134CD18F@powerusersbbs.com> References: <3A6C7007.134CD18F@powerusersbbs.com> <3A6B9008.88CCCE91@home.com> <20010122080422.A88843@citusc17.usc.edu> <3A6C64CE.DDA1F400@powerusersbbs.com> <20010122175500.O16921@wilbury.sk>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <3A6C7007.134CD18F@powerusersbbs.com> Ted Sikora writes: : That was it. How can root be dangerous in ssh.. isn't that why it : exists? Or would using su be better? I usually use ssh to remotely : administer the servers. Using su would be better. Root can be dangerous in ssh because it exposes your machines to outside agents that are able to login as root. It can be made to be allowed in the config file, but isn't by default due to this danger. Once you've set things up to allow only strong authentication methods for root, it is likely safe to remove it. However, it is even safer to use sudo or su to grant root access. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200101222101.f0ML1G912295>