Thanks Chuck: Yes I checked /etc/master.passwd. it has no "#" except first two lines:
# $FreeBSD: src/etc/master.passwd,v 22.214.171.124 2008/11/25 02:59:29 kensmith Exp $ # ... ... tester:$1$qM9hT7CJ$vUby0fxVPjgwH1JNe5j45.:2002:20::0:0:User &:/home/tester:/usr/local/bin/bash --- On Tue, 2/17/09, Chuck Swiger <cswi...@mac.com> wrote: > From: Chuck Swiger <cswi...@mac.com> > Subject: Re: freebsd and freeradius > To: ipfr...@yahoo.com > Cc: "freebsd general questions" <firstname.lastname@example.org> > Date: Tuesday, February 17, 2009, 10:54 AM > On Feb 17, 2009, at 10:44 AM, gahn wrote: > > No, there is no # in any lines of /etc/passwd. > > Did you check /etc/master.passwd also? > > > Btw, what is this "src/etc/master.passwd" > for? > > A line like: > > # $FreeBSD: src/etc/master.passwd,v 1.40 2005/06/06 > 20:19:56 brooks Exp $ > > ...indicates the CVS revision that the passwd file comes > from. It's mildly interesting when you run mergemaster > -iU or the like to update to a newer version of the OS to > pick up any default system accounts or changes which have > been made. > > If you're instead asking why there is a /etc/passwd > versus master.passwd, the former is historically expected > and is supposed to be world-readable, but the traditional > practice of putting encrypted passwords in there made > automated password cracking relatively feasible. Various > UNIXes responded to things like "John the Ripper" > by creating a second password database which contained the > encrypted passwords, called /etc/shadow in some places, or > /etc/master.passwd on FreeBSD, and having that only readable > by root. The old /etc/passwd file would then have an > "x" or "*" for the passwd field. > > Regards, > ---Chuck _______________________________________________ email@example.com mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"