From: Michael Albinus <michael.albinus@gmx.de>
To: Allen Li <vianchielfaura@gmail.com>
Cc: 29575@debbugs.gnu.org
Subject: bug#29575: 25.3; Secret Service API treats labels as unique
Date: Tue, 15 May 2018 14:56:22 +0200 [thread overview]
Message-ID: <87bmdh3wnd.fsf@gmx.de> (raw)
In-Reply-To: <87lgi87387.fsf@gmx.de> (Michael Albinus's message of "Tue, 12 Dec 2017 09:35:52 +0100")
Michael Albinus <michael.albinus@gmx.de> writes:
Hi Allen,
>>> Well, inside the org.freedesktop.Secret.{Service,Collection,Item}
>>> interfaces, an item is identified by an object path. We could extend our
>>> interface to allow both label and object path as item, and to throw away
>>> the "unique label rule" inside collections.
>>
>> That sounds like a better starting idea. One problem that comes to
>> mind is that the object path could be a valid label value, I think.
>
> That's possible, yes. But I doubt it will happen in reality. At least in
> Emacs we could check, that a label doesn't look like an object path, and
> suppress such items for being considered.
Finally, I found the time to implement this. `secrets-create-item' does
allow labels now which exist already in a collection. `secrets-item-path',
`secrets-get-secret', `secrets-get-attributes', 'secrets-get-attribute'
and `secrets-delete-item' allow also object paths as argument.
Pushed to the master branch. Could you pls check whether this fits your needs?
Best regards, Michael.
next prev parent reply other threads:[~2018-05-15 12:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 5:42 bug#29575: 25.3; Secret Service API treats labels as unique Allen Li
2017-12-11 13:02 ` Michael Albinus
2017-12-11 19:47 ` Allen Li
2017-12-12 8:35 ` Michael Albinus
2017-12-13 3:41 ` Allen Li
2017-12-13 14:41 ` Ted Zlatanov
2018-05-15 12:56 ` Michael Albinus [this message]
2018-05-21 7:51 ` Allen Li
2018-05-22 9:35 ` Michael Albinus
2018-09-05 9:00 ` Michael Albinus
2018-09-08 23:58 ` Allen Li
2018-09-11 9:49 ` 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=87bmdh3wnd.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=29575@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 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.