Date: Sat, 23 Jun 2012 10:13:25 -0700 From: Devin Teske <devin.teske@fisglobal.com> To: Clayton Milos <clay@milos.co.za> Cc: Devin Teske <dteske@freebsd.org>, Freebsd-stable@freebsd.org Subject: Re: [CFT] Need Testers for: sysutils/bsdconfig Message-ID: <3E067C84-46DD-4345-BEBA-A4D93B59B4B9@fisglobal.com> In-Reply-To: <082B913F-3A95-48C1-8B5A-BD220937748C@fisglobal.com> References: <2322BE6D-24A8-4F4A-84B2-4DFE33BCA65B@fisglobal.com> <4FE3EB9D.9070509@fuzzwad.org> <4FE419CD.60708@rdtc.ru> <F34D40AA-3AE4-4A1F-B521-CEC2A06ABC79@fisglobal.com> <4FE4245C.3040806@rdtc.ru> <90361FE2-2298-48E5-B8B6-2BA704781098@fisglobal.com> <4FE431C0.8040509@rdtc.ru> <006001cd5072$84247cd0$8c6d7670$@milos.co.za> <B622337A-28E4-443B-BAFD-ECF00F907A4D@fisglobal.com> <082B913F-3A95-48C1-8B5A-BD220937748C@fisglobal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 22, 2012, at 3:44 PM, Devin Teske wrote: >=20 > On Jun 22, 2012, at 3:32 PM, Devin Teske wrote: >=20 >>=20 >> On Jun 22, 2012, at 5:27 AM, Clayton Milos wrote: >>=20 >>>=20 >>> When selecting user account expiry the calendar starts at 1 January 197= 0. I >>> understand that this is when Unix time started but it would be nice for= it >>> to start from the current date. >>>=20 >>=20 >> This was on-purpose because there is a discrepancy in passwd(5) manual r= egarding what a value of zero (0) means for these fields. >>=20 >> From passwd(5): >>=20 >> The change field is the number of seconds from the epoch, UTC, unti= l the >> password for the account must be changed. This field may be left e= mpty >> to turn off the password aging feature. >>=20 >> Nowhere in the manual does it say that zero is a synonym to being left e= mpty. >>=20 >=20 > And yet, this is how the system treats zero (was my complaint). >=20 > The user root (and toor, and several other system users) come with a defa= ult value of zero for this field. >=20 > If zero was treated according to the manual, then root would be disabled = by default. But that's clearly not the case in a default installation which= has a value of zero. >=20 > So, when you're using bsdconfig to view an existing user that has a value= of zero, you will notice that the default calendar date/time that is chose= n corresponds to "zero seconds from the epoch, UTC", despite the fact that = I know (and you know) that zero is synonymous with NULL. >=20 > So I'm a fan of updating the man page and when that is done, I am happy t= o change bsdconfig to treat zero as-such. But right now I wanted to stay tr= ue to the manual (which plainly states that any non-NULL value is treated a= s seconds from the epoch). In an effort to get the passwd(5) manual updated (pre-requisite to fixing t= he bsdconfig(8) functionality to coincide with the manual change), I've fil= ed PR ports/169354. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=3D169354 --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E067C84-46DD-4345-BEBA-A4D93B59B4B9>