From: Michael Albinus <michael.albinus@gmx.de>
To: Allen Li <vianchielfaura@gmail.com>
Cc: 30246@debbugs.gnu.org
Subject: bug#30246: 25.2.50; auth-source does not support creation or deletion with secrets provider
Date: Thu, 25 Jan 2018 11:11:20 +0100 [thread overview]
Message-ID: <87y3kmdz93.fsf@gmx.de> (raw)
In-Reply-To: <CAJr1M6fypg=_xgsq5BrciVNYg1BToUKpurgFPGt5JR09+2NcnQ@mail.gmail.com> (Allen Li's message of "Wed, 24 Jan 2018 16:56:26 -0800")
Allen Li <vianchielfaura@gmail.com> writes:
Hi Allen,
> auth-source does not support saving secrets with the Secrets API
> backend. This reduces the usefulness of auth-source significantly
> since keychains that provide secure secret storage using the API are
> standard on many GNU/Linux distributions (e.g., gnome-keyring on
> Ubuntu).
This was reported already some years ago on the emacs-help ML, see
<http://lists.gnu.org/archive/html/help-gnu-emacs/2013-06/msg00361.html>. IIRC,
it wasn't trivial to implement, that's why it has lingered around on my
TODO since then.
See also `auth-source-secrets-create' in auth-source.el, which misses
its implementation. And you've got the error message "The Secrets API
auth-source backend doesn't support creation yet".
Since I am working on secrets.el these days anyway due to your other
report bug#29575, chances are good that I'll fix this, finally.
Best regards, Michael.
next prev parent reply other threads:[~2018-01-25 10:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 0:56 bug#30246: 25.2.50; auth-source does not support creation or deletion with secrets provider Allen Li
2018-01-25 10:11 ` Michael Albinus [this message]
2018-04-13 13:41 ` Michael Albinus
2018-04-16 1:51 ` Allen Li
2018-04-16 6:44 ` Michael Albinus
2018-09-05 8:57 ` Michael Albinus
2018-09-08 23:51 ` Allen Li
2018-09-11 10:26 ` Michael Albinus
2018-09-13 14:09 ` Michael Albinus
2018-04-23 8:43 ` Michael Albinus
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3kmdz93.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=30246@debbugs.gnu.org \
--cc=vianchielfaura@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).