From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] plan9 as an imaps server
Date: Tue, 29 May 2007 09:04:53 -0700 [thread overview]
Message-ID: <13426df10705290904v65b9eaf9ved756f75c74d5b2e@mail.gmail.com> (raw)
In-Reply-To: <79a2c0f525af81144e0304aafb4a1412@quintile.net>
On 5/29/07, Steve Simon <steve@quintile.net> wrote:
> I guess you know this but just in case - imap uses the inferno/pop password for
> your account on the plan9 box, rather than the p9sk1 one. This is visible on
> your machine (so authserv can see it) from the console of your machine, look in
> /mnt/keys/$user/secret (I think - not at the console at present). you could
> look in here to ensure you don't have a different inferno/pop(/imap) passowrd
> from the one you hoped.
>
actually, here is what is interesting. Once I put the key in
/mnt/factotum/ctl via cat, i.e. once I did this:
auth/secstore -G factotum > /mnt/factotum/ctl
then the mail passwords for all accounts -- port imap or imaps --
stopped working. They were working moments before this, then stopped.
Once I got rid of the factotum, they started working again. Now that's
confusing (to me).
I think the bigger issue is that the wiki is just almost, but not
quite, completely wrong on how to do this.
thanks
ron
p.s. this is in auth/password.c:
if(pw->expire <= now){
werrstr("account expired");
freePW(pw);
return nil;
}
I read yesterday that pw->expire == 0 means "forever". That's going to
always fail here, right?
how about if ((pw_expire) && (pw->expire <= now)){
next prev parent reply other threads:[~2007-05-29 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 6:48 ron minnich
2007-05-29 7:01 ` Skip Tavakkolian
2007-05-29 7:38 ` Steve Simon
2007-05-29 16:04 ` ron minnich [this message]
2007-05-29 16:10 ` erik quanstrom
2007-05-29 16:14 ` ron minnich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13426df10705290904v65b9eaf9ved756f75c74d5b2e@mail.gmail.com \
--to=rminnich@gmail.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).