Gnus development mailing list
 help / color / mirror / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: tramp-devel@mail.freesoftware.fsf.org, ding@gnus.org
Subject: Re: Passwords, stored in Gnome Keyring and KWallet
Date: Tue, 23 Feb 2010 14:38:50 +0100	[thread overview]
Message-ID: <871vgc2hsl.fsf@gmx.de> (raw)
In-Reply-To: <87vddp0zra.fsf@lifelogs.com>

[-- Attachment #1: Type: text/plain, Size: 918 bytes --]

Ted Zlatanov <tzz@lifelogs.com> writes:

Hi Ted,

> The only things we have to agree is how to pick an entry
> (auth-source-pick, but this is probably OK as is) and how to get the
> data out (auth-source-user-or-password, anything like
> netrc-machine-user-or-password will work).

See the Commentary section. You can define lookup attributes, which are
supposed to do exactly this. The examples I have used there match this
case :-)

> Sadly I don't see secrets.el in the Tramp repo currently.  Is it
> available?

I have not decided yet, whether to store it in Tramp's archive. If it is
used as backend for auth-sources, it might be better to keep it close to
this. I have added the current version to this message.

> Perhaps it's better to name it sec-serv.el or something similarly more
> descriptive?  It doesn't matter that much to me.

It doesn't matter too much to me as well.

> Ted

Best regards, Michael.


[-- Attachment #2: secrets.el --]
[-- Type: application/emacs-lisp, Size: 28467 bytes --]

[-- Attachment #3: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Tramp-devel mailing list
Tramp-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/tramp-devel

  reply	other threads:[~2010-02-23 13:38 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-20 14:47 Michael Albinus
2010-02-22 20:41 ` Ted Zlatanov
2010-02-23 13:38   ` Michael Albinus [this message]
2010-02-23 20:03     ` Ted Zlatanov
2010-02-24  8:28       ` Michael Albinus
2010-03-09 16:50         ` Ted Zlatanov
2010-03-10 21:06           ` Michael Albinus
2010-03-20 19:47             ` Ted Zlatanov
2010-03-23 18:06             ` Ted Zlatanov
2010-03-23 18:23               ` Ted Zlatanov
2010-03-27 19:04               ` Ted Zlatanov
2010-03-29  5:00                 ` Katsumi Yamaoka
2010-03-29  6:51                   ` Norbert Koch
2010-03-29  7:04                     ` Katsumi Yamaoka
2010-03-29  7:48                       ` Norbert Koch
2010-03-29  9:26                   ` Ted Zlatanov
2010-05-12 12:07                 ` Michael Albinus
2010-05-12 12:30                   ` Ted Zlatanov
2010-05-12 13:06                     ` Michael Albinus
2010-05-16 18:39                     ` Michael Albinus
2010-05-18 19:50                       ` Michael Albinus
2010-06-07 16:28                       ` Ted Zlatanov
2010-06-08 13:55                         ` Michael Albinus
2010-06-07 16:41                   ` Ted Zlatanov
2010-06-08 13:56                     ` Michael Albinus
2010-06-08 14:34                       ` Ted Zlatanov
2010-03-11 11:46           ` Steinar Bang
2010-03-11 13:24             ` 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=871vgc2hsl.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=ding@gnus.org \
    --cc=tramp-devel@mail.freesoftware.fsf.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).