From: Javier Olaechea <pirata@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Philip Kaludercic <philipk@posteo.net>, 55199@debbugs.gnu.org
Subject: bug#55199: 28.1; rcirc auth-source integration doesn't handle port being a number
Date: Sun, 21 Aug 2022 14:02:21 -0500 [thread overview]
Message-ID: <CAFVS=zASaZy=N7dXzc5nOvnwMJpqKE_gmf8XYBh4wNzqdaWmDA@mail.gmail.com> (raw)
In-Reply-To: <878rnim3cf.fsf@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 2040 bytes --]
Hi Michael,
I can confirm patch fixes the issue. I don't think we need to change the
create function. The issue is that a valid spec, meant for another backend,
results in an error when searching the secrets backend.
An alternative solution would be for auth-source-secrets-search to return
an empty list (no secrets found iirc) when the spec contains a non-string
value.
On Sun, Aug 21, 2022 at 3:02 AM Michael Albinus <michael.albinus@gmx.de>
wrote:
> Javier Olaechea <pirata@gmail.com> writes:
>
> Hi Javier,
>
> > I have a simple way to reproduce the issue. Start emacs with emacs -Q.
> > Then evaluate the following snippet
> >
> > (require 'auth-source)
> >
> > (let ((auth-sources '("secrets:Login")))
> > (auth-source-search :port 6697))
>
> Yep. Fails here as well.
>
> > So the issue is not at all on rcirc, but that secrets backend assumes
> > that the search specs should be strings. I haven't researched the
> > SecretService API to know if this is a restriction of the underlying
> > dbus service the secrets backend works with or just a restrictive
> > assumption of the code in secrets.el.
>
> The Secret Service API allows only strings for attribute keys and
> values, see <
> https://specifications.freedesktop.org/secret-service/latest/re03.html>:
>
> --8<---------------cut here---------------start------------->8---
> READWRITE Dict<String,String> Attributes ;
> --8<---------------cut here---------------end--------------->8---
>
> Looking at auth-source.el. there was a similar problem in
> auth-source-plstore-search, see commit
> fcb89237d9ab969bcd29bf8f8fae8d9905644b92 in Emacs git. Applying a
> similar change to auth-source-secrets-search let the error go away.
>
> I've appended the patch, could you pls check in the rcirc context? I'm
> also not sure whether we need to change something when creating an item
> in auth-source-secrets-create.
>
> Best regrads, Michael.
>
>
--
"I object to doing things that computers can do." — Olin Shivers
[-- Attachment #2: Type: text/html, Size: 2817 bytes --]
next prev parent reply other threads:[~2022-08-21 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 19:15 bug#55199: 28.1; rcirc auth-source integration doesn't handle port being a number Javier Olaechea
2022-05-18 23:26 ` Philip Kaludercic
2022-06-11 3:46 ` Javier Olaechea
2022-08-21 6:00 ` Javier Olaechea
2022-08-21 8:02 ` Michael Albinus
2022-08-21 19:02 ` Javier Olaechea [this message]
2022-08-22 15:05 ` 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='CAFVS=zASaZy=N7dXzc5nOvnwMJpqKE_gmf8XYBh4wNzqdaWmDA@mail.gmail.com' \
--to=pirata@gmail.com \
--cc=55199@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=philipk@posteo.net \
/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).