From: Ted Zlatanov <tzz@lifelogs.com>
To: Thomas Hisch <t.hisch@gmail.com>,
Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: Loading credentials from login keyring
Date: Thu, 31 Dec 2020 10:14:31 +0000 [thread overview]
Message-ID: <mtxuwad4.fsf@lifelogs.com> (raw)
In-Reply-To: <CA+e_QifoScYkmbsPL2ZPk8aYqoGh4h8S5+VgKJtj8PGsM=Y2fg@mail.gmail.com> (Thomas Hisch's message of "Tue, 29 Dec 2020 20:33:13 +0100")
On Tue, 29 Dec 2020 20:33:13 +0100 Thomas Hisch <t.hisch@gmail.com> wrote:
TH> I created the credentials using the python-keyring [2] pkg using the command
TH> `keyring set hostname username`
TH> The above command creates an entry in the Login keyring that has the
TH> following schema (output of `M-x secrets-show-secrets`)
TH> `-[-] Password for ’thomas.hisch’ on ’hostname’
TH> |- password: ********** [Show password]
TH> |- application: Python keyring library
TH> |- service: hostname
TH> |- username: thomas.hisch
TH> `- xdg:schema: org.freedesktop.Secret.Generic
TH> The problem now is that `auth-source-user-and-password` doesn't find the
TH> credentials in the "Login" keyring, i.e.,
TH> (let ((auth-sources '("secrets:Login")))
TH> (auth-source-user-and-password "hostname"))
TH> returns nil. The reason for this is that `auth-source-user-and-password`
TH> searches for an entry with a plist key :host and not with the key :service.
If there will never be a :host in the Login keyring, I have no objection
to mapping :service to :host on the backend or specifically in
`auth-source-user-and-password`. But I don't know if that will break any
existing use cases.
Michael, WDYT?
Thanks
Ted
next prev parent reply other threads:[~2020-12-31 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 19:33 Loading credentials from login keyring Thomas Hisch
2020-12-31 10:14 ` Ted Zlatanov [this message]
2020-12-31 15:19 ` Michael Albinus
2020-12-31 15:18 ` Michael Albinus
2021-01-01 9:08 ` Thomas Hisch
2021-01-01 10:25 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mtxuwad4.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=t.hisch@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.