[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] post now asking for a password, even when it doesn't h
From: |
David Levine |
Subject: |
Re: [Nmh-workers] post now asking for a password, even when it doesn't have to |
Date: |
Mon, 14 Apr 2014 23:14:22 -0400 |
Ken wrote:
> It turns out even though I tested this, I wasn't actually using some of
> the backend programs until now ... like post. D'oh!
>
> Anyway, I discovered that now post(8) is always asking me for a username
> and password ... even when it doesn't need to (my sasl mechanism doesn't
> require them).
I didn't expect that: I thought that a username and password were
always required here.
> The change that caused this is b9763fdd7e96e7ac8bdb1, and
> the key issue is that in the third argument for sm_get_credentials() is
> now "0", instead of "1" (like it used to be).
>
> I went back and looked at the mailing list, and that discussion was here:
>
> http://lists.nongnu.org/archive/html/nmh-workers/2013-05/msg00005.html
If that argument is changed to "1", it breaks Valdis's use case.
I think that the nmh_get_credentials() call needs to move back
to sm_get_pass(). We might want to do that with inc and msgchk,
too.
> But I guess I don't understand why post now behaves differently than inc
> and msgchk, which are also sasl-aware programs. Can someone fill me in
> here?
My read of the code was that post did behave differently than
inc and msgchk. See commit 52a236230220, the diffs of the inc.c
and msgchk.c are straightforward.
David