Gnus development mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org, Tramp Development List <tramp-devel@gnu.org>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: global authinfo mechanism in Emacs, Gnus, Tramp
Date: Thu, 28 Feb 2008 09:12:04 -0700	[thread overview]
Message-ID: <m3hcftm563.fsf@fleche.redhat.com> (raw)
In-Reply-To: <86bq61m6ph.fsf_-_@lifelogs.com> (Ted Zlatanov's message of "Thu\, 28 Feb 2008 09\:38\:50 -0600")

>>>>> "Ted" == Ted Zlatanov <tzz@lifelogs.com> writes:

Ted> I'm tired of specifying special variables for authentication everywhere
Ted> in Emacs and in Gnus.  I see a *lot* of questions about setting those
Ted> up in Gnus, as well, so I think we can do better.

Additionally it would be nice not to have to set the variables by hand
at all... Emacs could remember the passwords in a keyring.

Ted> entry:
Ted>  protocol-or-purpose: ['pop, 'imap, 'imaps, 'ssh, t]
Ted>   hardcoded: (:user "me" :password 'ask :cache 60)
Ted>   file: (:name "/a/b/c" :epg-parameters () :other-parameters ())
Ted>   command: (:program "/bin/true" :parameters ())

Gnome's keyring manager uses (more or less) an application-specified
alist and returns the best match.  That way different users of the
keyring can store the information they need there.

Tom



  reply	other threads:[~2008-02-28 16:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 20:37 mail-source.el patch to use netrc-parse Ted Zlatanov
2008-02-16 22:21 ` Reiner Steib
2008-02-28 15:38   ` Ted Zlatanov
2008-04-25 18:52     ` Ted Zlatanov
2008-02-28 15:38   ` global authinfo mechanism in Emacs, Gnus, Tramp (was: mail-source.el patch to use netrc-parse) Ted Zlatanov
2008-02-28 16:12     ` Tom Tromey [this message]
2008-02-28 18:03       ` global authinfo mechanism in Emacs, Gnus, Tramp Ted Zlatanov
2008-02-28 17:48         ` Tom Tromey
2008-03-06 22:36     ` 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=m3hcftm563.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=tramp-devel@gnu.org \
    --cc=tzz@lifelogs.com \
    /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).