From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <13426df10705282321o5721fe8dh880e795b06a0dc1c@mail.gmail.com>
Date: Mon, 28 May 2007 23:21:24 -0700
From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] I'm puzzled
In-Reply-To: <14ec7b180705282251o1c33488fg840a9a9fac54dfb3@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <13426df10705282113iec0fa05hcf85679888b9a12d@mail.gmail.com>
	<5429cae9062c140902d55e19059873bf@plan9.bell-labs.com>
	<14ec7b180705282251o1c33488fg840a9a9fac54dfb3@mail.gmail.com>
Topicbox-Message-UUID: 742348c2-ead2-11e9-9d60-3106f5b1d025

On 5/28/07, andrey mirtchovski <mirtchovski@gmail.com> wrote:
> how does that deal with the "never" expiring accounts, don't they have
> zero as the expiry date?
>
> On 5/28/07, geoff@plan9.bell-labs.com <geoff@plan9.bell-labs.com> wrote:
> > I've just pushed out a new auth/secstore/password.c that has better
> > error messages and only believes non-zero expiry times.
> >
> >
>
BTW, the auth/enable did not work at all.

I am running, right now, with a hacked secstored (well, password.c is
hacked with an 'expired, like I care' print to fd 2) that ignores the
expired error. I have no idea what's wrong here. I just know how to
work around it.

thanks

ron