Repository navigation
Replies: 4 comments
|
Currently, the whole API is build around oo7::file::UnlockedKeyring which is using the V1 format of gnome-keyring. Adding a new format would mean creating an enum variant that supports all those possible implementations and their quirks. I am not against it, but at this point, keepass already had a freedesktop secret dbus interface implemntation no? why not use it directly? |
|
I use I planned a SecretService on top of kpdx files way back in 2015 or so (it was my second attempted Rust project) but got mired in the lack of a D-Bus API at the time. The main goal was to have per-app permission to specific secrets (e.g., app A shouldn't have access to any password, just those I've allowed access to). I'm also interested in the portal implementation. |
That is unfortunately not possible as you can't tell what app is running without something like systemd-appd. In any case, the project is open source, feel free to look into it and submit patches that might make it more useful for you. No promise they will all get merged as is, but we can figure that out with time. Please let me know before doing any major work tho. |
For sure; that was the goal behind the issue after all :) .
Hrm. I thought I saw a path for this somewhere, but it's been so long. Maybe I had RFE issues I planned to file…anyways, I'll take a look at |
Uh oh!
There was an error while loading. Please reload this page.
I use KeePass files for my passwords. Is there willingness to add/accept support for using them as a backing filesystem store? Perhaps it could be done from outside of this repo in some way (not sure; haven't dug into the architecture)?
All reactions