Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: nnimap-authinfo-file customization proposes "inline" format
Date: Mon, 10 Nov 2008 16:00:31 -0600	[thread overview]
Message-ID: <86wsfbkzr4.fsf@lifelogs.com> (raw)
In-Reply-To: <87d4hbz60z.fsf@gmail.com>

On Tue, 04 Nov 2008 19:43:08 +0100 Paul R <paul.r.ml@gmail.com> wrote: 

PR> On Tue, 04 Nov 2008 10:51:51 -0600, Ted Zlatanov <tzz@lifelogs.com> said:
Ted> I'd like at least one more person to use it and let us know if it's
Ted> OK. Otherwise we'll commit to CVS in a week (to give us time to
Ted> find potential bugs).

PR> Yes, that's wise. Keep in mind that I now only use the patched function
PR> with already-built lists, and never with netrc file path, so although
PR> I can say that it works flowlessly my way, I have no idea about any
PR> regression in netrc file parsing.

PR> Also, if you want to commit, you may want to change the docstring and
PR> the parameter name to reflect new versatility.

I comitted the change.

I think it's better to leave this undocumented, I'd rather push people
towards using a netrc file.  Then they can store it with GPG encryption
separately from the rest of their configuration, which is the better
practice IMHO.

If you and others feel that Gnus should explicitly discuss and promote
inline password storage in addition to GPG-encrypted netrc files, please
let me know.

Either way, I should write a guide for setting up netrc files for Gnus
and Emacs in general, using auth-source.el which I comitted recently.

Thanks
Ted




  reply	other threads:[~2008-11-10 22:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30 21:00 Paul R
2008-10-31 17:36 ` Ted Zlatanov
2008-10-31 18:42   ` Paul R
2008-11-03 21:02     ` Ted Zlatanov
2008-11-03 23:31       ` Paul R
2008-11-04 16:51         ` Ted Zlatanov
2008-11-04 18:43           ` Paul R
2008-11-10 22:00             ` Ted Zlatanov [this message]
2009-02-13 22:38               ` auth-source documentation (was: nnimap-authinfo-file customization proposes "inline" format) Ted Zlatanov

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=86wsfbkzr4.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).