unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Javier Olaechea <pirata@gmail.com>
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 10:02:24 +0200	[thread overview]
Message-ID: <878rnim3cf.fsf@gmx.de> (raw)
In-Reply-To: <CAFVS=zCXy-g=xK_F=dXb6DOSYZeauhPkYuXWGFyc6JP9COcpDw@mail.gmail.com> (Javier Olaechea's message of "Sun, 21 Aug 2022 01:00:48 -0500")

[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]

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.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 1226 bytes --]

diff --git a/lisp/auth-source.el b/lisp/auth-source.el
index f198362f10..c79e5b81f7 100644
--- a/lisp/auth-source.el
+++ b/lisp/auth-source.el
@@ -1618,10 +1618,13 @@ auth-source-secrets-search
          (search-specs (auth-source-secrets-listify-pattern
                         (apply #'append (mapcar
                                       (lambda (k)
-                                        (if (or (null (plist-get spec k))
-                                                (eq t (plist-get spec k)))
-                                            nil
-                                          (list k (plist-get spec k))))
+                                        (let ((v (plist-get spec k)))
+                                          (if (or (null v)
+                                                  (eq t v))
+                                              nil
+                                            (list
+                                             k
+                                             (auth-source-ensure-strings v)))))
                                       search-keys))))
          ;; needed keys (always including host, login, port, and secret)
          (returned-keys (delete-dups (append

  reply	other threads:[~2022-08-21  8: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 [this message]
2022-08-21 19:02         ` Javier Olaechea
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=878rnim3cf.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=55199@debbugs.gnu.org \
    --cc=philipk@posteo.net \
    --cc=pirata@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).