From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: sieve-manage no longer works without authinfo
Date: Mon, 07 Mar 2011 09:46:29 -0600 [thread overview]
Message-ID: <87d3m33pd6.fsf@lifelogs.com> (raw)
In-Reply-To: <sa3aah7vsxi.fsf@cigue.easter-eggs.fr>
On Mon, 07 Mar 2011 16:42:01 +0100 Julien Danjou <julien@danjou.info> wrote:
JD> Btw, I'm suprised by the code you added that check if the :password is a
JD> function and then call it. Isn't that something which should be handled
JD> by auth-source rather than its user? Or I miss something else.
Unfortunately Emacs Lisp doesn't offer a better way to hide secret data.
So this is how we have to hide passwords in stack traces, debug
messages, etc. See also
http://permalink.gmane.org/gmane.emacs.gnus.general/77536 ("Re: Password protection")
where Lars and I talked about it.
Ted
next prev parent reply other threads:[~2011-03-07 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 6:04 Michael Welsh Duggan
2011-03-07 11:16 ` Ted Zlatanov
2011-03-07 14:33 ` Julien Danjou
2011-03-07 15:30 ` Ted Zlatanov
2011-03-07 15:42 ` Julien Danjou
2011-03-07 15:46 ` Ted Zlatanov [this message]
2011-03-08 1:36 ` Michael Welsh Duggan
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=87d3m33pd6.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/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).