Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: tzz-auth-source-rewrite branch (was: [gnus git]  branch tzz-auth-source-rewrite created: =0=)
Date: Sun, 06 Feb 2011 08:59:44 -0600	[thread overview]
Message-ID: <87zkq9tdi7.fsf_-_@lifelogs.com> (raw)
In-Reply-To: <87ei7nivte.fsf@lifelogs.com>

On Fri, 04 Feb 2011 10:55:09 -0600 Ted Zlatanov <tzz@lifelogs.com> wrote: 

TZ> This is a branch for my auth-source.el rewrite.  It has the latest
TZ> working version.

I added Secrets API support (search only, no create or delete) and
`auth-source-user-or-password' compatibility, plus I rebased the
branch.  I think the Secrets API should use the :max parameter if
possible so we don't get too many results at the top level.  Also it
seems quite slow to get the results one by one so maybe we can optimize
`secrets-search-items'.  Finally, Google Chrome stores passwords in
there but with a different scheme.  I wonder if it's useful to add
specific support for mapping those to the auth-source tokens (host,
protocol, user) or if I should put that special code in url.el only.

The `auth-source-user-or-password' wrapper tries to create an entry
currently, which is not OK.  So it's not ready for use.  When I think
it's OK, I'll update the manual and merge the branch back into the
master branch.

Ted




  reply	other threads:[~2011-02-06 14:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1PlOrx-0002M3-00@quimby.gnus.org>
2011-02-04 16:55 ` [gnus git] branch tzz-auth-source-rewrite created: =0= Ted Zlatanov
2011-02-06 14:59   ` Ted Zlatanov [this message]
2011-02-06 17:05     ` tzz-auth-source-rewrite branch Lars Ingebrigtsen
2011-02-07 20:47       ` Ted Zlatanov
2011-02-08 22:28         ` Ted Zlatanov
2011-02-09 21:36           ` Ted Zlatanov
2011-02-14  3:28             ` Lars Ingebrigtsen
2011-02-14  3:28         ` Lars Ingebrigtsen
2011-02-14 15:03           ` Ted Zlatanov
2011-02-14 17:58           ` Andreas Schwab
2011-02-06 18:38     ` Michael Albinus
2011-02-06 19:33       ` Ted Zlatanov
2011-02-06 20:36         ` Michael Albinus
2011-02-07 18:14           ` 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=87zkq9tdi7.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).