Date: Fri, 2 Nov 2001 10:00:28 +0100 From: "Anthony Atkielski" <anthony@atkielski.com> To: "Erik Trulsson" <ertr1013@student.uu.se> Cc: "Mike Meyer" <mwm@mired.org>, <questions@FreeBSD.ORG> Subject: Re: Lockdown of FreeBSD machine directly on Net Message-ID: <00d801c1637c$d3264640$0a00000a@atkielski.com> References: <15330.23714.263323.466739@guru.mired.org> <00b501c1637b$1cd2f880$0a00000a@atkielski.com> <20011102095554.A38169@student.uu.se>
next in thread | previous in thread | raw e-mail | index | archive | help
Erik writes: > You should not log in directly as root. What > you should do is login as a normal user and > then use 'su' to become root. Since everyone keeps telling me this, I guess this is what I'll do. However, I'd still like to know what has to be done to make SSH work for root logins. The "Sorry, you are not allowed to connect" message must be coming from somewhere, and it seems to be specific to root. I've restarted sshd (in fact, I've restarted the system), so it's not that. > This requires that the user you login as is > in the 'wheel' group. And if I add that user to wheel, does that open up any other holes? Doesn't wheel have a lot of permissions on a lot of files? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00d801c1637c$d3264640$0a00000a>