From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Severe limitations in auth-source-macos-keychain-search
Date: Mon, 25 Jan 2016 09:57:06 -0500 [thread overview]
Message-ID: <87twm1pv0d.fsf@lifelogs.com> (raw)
In-Reply-To: <CADdV=MtDq0asg8DJUYtOgLTipN5j3pg5oWC=Q04AcNebE-9NLg@mail.gmail.com>
On Fri, 8 Jan 2016 09:36:56 +0100 Nikolai Weibull <now@disu.se> wrote:
NW> Is anyone actually using auth-source-macos-keychain-search (with Gnus)?
Not with Gnus.
NW> If so, how do you get it to work? As far as I can tell, this function
NW> doesn’t take into account that spec may contain keys that are lists,
NW> for example, host and port.
NW> Furthermore, in auth-source-macos-keychain-search-items, if called for
NW> macos-keychain-generic, should probably validate that -c and -r only
NW> receive four-letter values, as that’s what security(1) requires them
NW> to be.
Can you either try to write a patch against auth-source.el, or explain
in more detail how it should operate?
I have access to a Mac OS X machine, but I don't know enough about the
keychain to understand exactly what needs to be done.
Thanks
Ted
next prev parent reply other threads:[~2016-01-25 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 8:36 Nikolai Weibull
2016-01-25 14:57 ` Ted Zlatanov [this message]
2016-01-25 16:17 ` Jeff Bellegarde
2016-02-06 6:00 ` Lars Ingebrigtsen
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=87twm1pv0d.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).