Date: Sun, 20 May 2007 23:48:32 -0700 From: Garrett Cooper <youshi10@u.washington.edu> To: Chad Perrin <perrin@apotheon.com> Cc: 'Anton Galitch' <anton.galitch@gmail.com>, "Tamouh H." <hakmi@rogers.com>, questions@freebsd.org, 'Ted Mittelstaedt' <tedm@toybox.placo.com> Subject: Re: just general questions about fbsd Message-ID: <465140C0.7070409@u.washington.edu> In-Reply-To: <20070521044430.GB91151@demeter.hydra> References: <20070520221917.GA91736@ezekiel.daleco.biz> <BMEDLGAENEKCJFGODFOCCEBHCAAA.tedm@toybox.placo.com> <1a9901c79b3c$4774abc0$6600a8c0@tamouh> <20070521044430.GB91151@demeter.hydra>
next in thread | previous in thread | raw e-mail | index | archive | help
Chad Perrin wrote: > On Sun, May 20, 2007 at 08:09:19PM -0400, Tamouh H. wrote: >> On the other hand, Windows has the ability to change the administrator user or completely disable it. Something not available in Unix systems. For example, a cracker or hacker targeting UNIX system will automatically try to compromise the "root" user. It is 100% guaranteed to be there. On the other hand in Windows, good sys admins will rename or complete disable the administrator user hence making it more difficult to know the administrator user. >> > > Actually . . . technically, root users can be renamed and can, in many > ways, be disabled. They can certainly be made inaccessible remotely. > That can break many scripts though, can't it, if the dev improperly looks up the name, not the UID? -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?465140C0.7070409>