[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 soredake changed: What|Removed |Added CC|katyaberezy...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 h...@runiq.de changed: What|Removed |Added CC||h...@runiq.de -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216
`{third: "Beedell", first: "Roke"}`{.JSON5}
<4wy78...@rokejulianlockhart.addy.io> changed:
What|Removed |Added
CC||4wy78uwh@rokejulianlockhart
||.addy.io
--
You are receiving this mail because:
You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 mpeter.68...@simplelogin.co changed: What|Removed |Added CC||mpeter.68...@simplelogin.co -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Bernd Steinhauser changed: What|Removed |Added CC||li...@bernd-steinhauser.de -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 michaelk83 changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=458318 --- Comment #39 from michaelk83 --- (In reply to michaelk83 from comment #36) > (In reply to soredake from comment #35) > > https://invent.kde.org/frameworks/kwallet/-/merge_requests/11 > > This has now been merged and released in KDE Frameworks 5.97.0. This can > probably be marked as resolved. After more testing, it looks like the implementation is still broken/incomplete in a few places. See the blockers for Bug 458318, among lesser issues. -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 --- Comment #38 from michaelk83 --- (In reply to Björn Bidar (Thaodan) from comment #34) > (In reply to Alexander Schlarb from comment #33) > > (In reply to Thaodan from comment #32) > > > (In reply to Alexander Schlarb from comment #29) > > > > > > > Finally, how would you feel about replacing the existing KWallet daemon > > > > with > > > > a proxy implementation that forwards all calls on the KWallet D-Bus API > > > > to > > > > org.freedesktop.Secrets/KeePassXC? ... > > > > > > This could break usescases that use GPG to encrypt the password database. > > > > I see, didn't know KWallet could do that. Is this a blocker though? When do > > people actually use this option over master passwords (and especially the > > auto-unlock with login password option)? > > When they want to secure the wallet by more then a password, especially when > the authentication method is separate from the computer e.g. on smartcard. > This also allows to cache the authentication to limit the time the wallet > can be opened without opening the authentication method again. > > This is also a part of a central authentication with a key instead of a > password and allows physical separation from the device that requests the > authentication and they one that stores the secret that is unlocked. > This then allows to remove the physical token when the user leaves the > computer. If KWallet daemon is replaced by a proxy forwarding to KeePassXC (or some other Secret Service provider), then encryption is handled by the Secret Service provider, so GPG is no longer needed. Of course, the user would have to choose, either use the full KWallet + GPG, or proxy + Secret Service backend. A similar idea was proposed in https://github.com/keepassxreboot/keepassxc/issues/3679#issuecomment-578498231 . Specifically KeePassXC already supports using an external key file or device (YubiKey et al) as one of the DB credentials. It has configurable auto-lock time limit. There are also plans for QuickUnlock using PIN or fingerprint, though not yet supported on Linux. So I think KeePassXC already covers the GPG use case. However, we're now seeing this issue with the new native support for Secret Service API in KWallet Framework 5.97.0: see Bug 458085 comment 13. -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 michaelk83 changed: What|Removed |Added CC||m...@apache.org --- Comment #37 from michaelk83 --- *** Bug 234434 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 michaelk83 changed: What|Removed |Added CC||mk.mat...@gmail.com --- Comment #36 from michaelk83 --- (In reply to soredake from comment #35) > https://invent.kde.org/frameworks/kwallet/-/merge_requests/11 This has now been merged and released in KDE Frameworks 5.97.0. This can probably be marked as resolved. -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Martino Fontana changed: What|Removed |Added CC||tinozzo...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Rokku changed: What|Removed |Added CC||d...@strace.it -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Sébastien Ménard changed: What|Removed |Added CC||kde-b...@smenard.io -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Celeste changed: What|Removed |Added CC||coelacant...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 brent.sa...@gmail.com changed: What|Removed |Added CC||brent.sa...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 prettyvani...@posteo.at changed: What|Removed |Added CC||prettyvani...@posteo.at -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 --- Comment #35 from soredake --- https://invent.kde.org/frameworks/kwallet/-/merge_requests/11 -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Luis Miguel García Mancebo changed: What|Removed |Added CC|kte...@ktecho.com | -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 --- Comment #34 from Thaodan --- (In reply to Alexander Schlarb from comment #33) > (In reply to Thaodan from comment #32) > > (In reply to Alexander Schlarb from comment #29) > > > > > Finally, how would you feel about replacing the existing KWallet daemon > > > with > > > a proxy implementation that forwards all calls on the KWallet D-Bus API to > > > org.freedesktop.Secrets/KeePassXC? At this point we're back to “+1”s of > > > course, but if done properly, KWalletManager and all existing KWallet > > > clients should continue to work and, as a future endeavour, KeePassXC > > > could > > > be stripped of its GUI and simply run as a daemon in the background while > > > supporting the well-established KDBX2 database format with native sync > > > support, as well as having browser integration and of course the > > > org.freedesktop.Secrets API. > > This could break usescases that use GPG to encrypt the password database. > > I see, didn't know KWallet could do that. Is this a blocker though? When do > people actually use this option over master passwords (and especially the > auto-unlock with login password option)? When they want to secure the wallet by more then a password, especially when the authentication method is separate from the computer e.g. on smartcard. This also allows to cache the authentication to limit the time the wallet can be opened without opening the authentication method again. This is also a part of a central authentication with a key instead of a password and allows physical separation from the device that requests the authentication and they one that stores the secret that is unlocked. This then allows to remove the physical token when the user leaves the computer. -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 --- Comment #33 from Alexander Schlarb --- (In reply to Thaodan from comment #32) > (In reply to Alexander Schlarb from comment #29) > > > Finally, how would you feel about replacing the existing KWallet daemon with > > a proxy implementation that forwards all calls on the KWallet D-Bus API to > > org.freedesktop.Secrets/KeePassXC? At this point we're back to “+1”s of > > course, but if done properly, KWalletManager and all existing KWallet > > clients should continue to work and, as a future endeavour, KeePassXC could > > be stripped of its GUI and simply run as a daemon in the background while > > supporting the well-established KDBX2 database format with native sync > > support, as well as having browser integration and of course the > > org.freedesktop.Secrets API. > This could break usescases that use GPG to encrypt the password database. I see, didn't know KWallet could do that. Is this a blocker though? When do people actually use this option over master passwords (and especially the auto-unlock with login password option)? -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Thaodan changed: What|Removed |Added CC||m...@thaodan.de --- Comment #32 from Thaodan --- (In reply to Alexander Schlarb from comment #29) > Finally, how would you feel about replacing the existing KWallet daemon with > a proxy implementation that forwards all calls on the KWallet D-Bus API to > org.freedesktop.Secrets/KeePassXC? At this point we're back to “+1”s of > course, but if done properly, KWalletManager and all existing KWallet > clients should continue to work and, as a future endeavour, KeePassXC could > be stripped of its GUI and simply run as a daemon in the background while > supporting the well-established KDBX2 database format with native sync > support, as well as having browser integration and of course the > org.freedesktop.Secrets API. This could break usescases that use GPG to encrypt the password database. -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Méven Car changed: What|Removed |Added CC||meve...@gmail.com --- Comment #31 from Méven Car --- *** Bug 430462 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Florian Lindner changed: What|Removed |Added CC||florian.lind...@xgm.de -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Ilya Bizyaev changed: What|Removed |Added CC||bizy...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 --- Comment #30 from Christoph Feck --- We didn't find a new contributor to continue KSecretService and/or rework KWallet to improve it or integrate it with other password wallet solutions. -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 --- Comment #29 from Alexander Schlarb --- I would really appreciate any update from anybody related in any position to the KSecretService project. Also, I would appreciate answers to the following questions: (If they sound like they are written by somebody who feels like there is little future for the existing KWallet/KSecretService plans then that is just my personal bias, definitely prove me wrong if you feel this to be unjust sentiment!) >From what I can tell, this project is dead, never had a working release and at this point it does not appear as if anybody is interested in picking it up again; is this observation accurate? And if that is indeed the case: Are future plans focused entirely around maintaining the existing KWallet system or is there any plans / interest beyond mere “+1”s to extend/replace that ecosystem with something else? Finally, how would you feel about replacing the existing KWallet daemon with a proxy implementation that forwards all calls on the KWallet D-Bus API to org.freedesktop.Secrets/KeePassXC? At this point we're back to “+1”s of course, but if done properly, KWalletManager and all existing KWallet clients should continue to work and, as a future endeavour, KeePassXC could be stripped of its GUI and simply run as a daemon in the background while supporting the well-established KDBX2 database format with native sync support, as well as having browser integration and of course the org.freedesktop.Secrets API. -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 --- Comment #28 from Alexander Schlarb --- @Guo Yunhe: I'm not sure if you are aware, but you could use KeePassXC instead as it implements the org.freedesktop.Secrets API since 2.5 and does a good job at it. It's database can also be synced without any issues. -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Guo Yunhe changed: What|Removed |Added CC||i...@guoyunhe.me --- Comment #27 from Guo Yunhe --- Really want this feature! Nowadays, all Electron applications depends on org.freedesktop.secrets and I have to install GNOME Keyrings to make it work. -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 ruruoli changed: What|Removed |Added CC||maniikarab...@protonmail.ch -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 kolAflash changed: What|Removed |Added CC||kolafl...@kolahilft.de -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Postix changed: What|Removed |Added Status|ASSIGNED|CONFIRMED --- Comment #26 from Postix --- I don't believe this task is still assigned to Valentin Rusu. Please feel to revert if you disagree. -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Christoph Feck changed: What|Removed |Added CC||deced...@gmail.com --- Comment #25 from Christoph Feck --- *** Bug 425561 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Cherkah changed: What|Removed |Added CC||cherifkah...@gmail.com --- Comment #24 from Cherkah --- just a copy and past to this post https://forum.kde.org/viewtopic.php?f=15&t=156925 so as to renew the quetion related to kwallet and secret service: ' What is the status of KWallet development now in KDE? Does it have a developer, that plan to improve it? Main problem for me is missing sync passwords between different Linux systems. KWallet sync feature was planned many years ago, but still no progress. Workarounds via manually syncing kwallet.kwl file got more problems, that profit, here is detailed description: https://bugs.kde.org/show_bug.cgi?id=403648 Also there was be plans to implement KSecretService as replacement to KWallet https://community.kde.org/KSecretService but seems it also stopped. Now Linux have those popular password storage implementations: KDE use KWallet that missing sync feature Gnome Keyring use Secret Service - https://specifications.freedesktop.org/secret-service/ pass, named as "the standard unix password manager" - https://www.passwordstore.org/ with QtPass GUI https://qtpass.org/ KeePassXC https://github.com/keepassxreboot/keepassxc that try to implement support for libsecret/DBus https://github.com/keepassxreboot/keepassxc/issues/1403 Qt apps use QtKeychain as API to access system password storage If KWallet development was stopped and no plan to improve it, which project we can recommend to select as alternative? ' -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 --- Comment #23 from Syiad --- +1 and add a PAM module for keepassxc, to enable opening the last used database at login. -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 hoperidesal...@protonmail.ch changed: What|Removed |Added CC||hoperidesalone@protonmail.c ||h --- Comment #22 from hoperidesal...@protonmail.ch --- Another vote for KeePassXC and and even maybe adding it to the KDE ecosystem. -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 --- Comment #21 from Andreas Schneider --- The solution would probably that KDE starts to use https://github.com/frankosterfeld/qtkeychain -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 --- Comment #20 from Andreas Schneider --- keepassxc version 2.5.0 has been release and offers a org.freedesktop.secrets service now! It would be great if applications would prefer to check org.freedesktop.secrets first before trying org.kde.kwalletd5! -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Andreas Schneider changed: What|Removed |Added CC||a...@cryptomilk.org -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 --- Comment #19 from 61.1...@gmail.com --- My impression is that system-level credential storage is usually used to save tokens. They are sensitive enough to be stored _somewhere_ better than scattered text files, but still not too important that you want to carry around and go through a long threat model analysis to protect it. It just appears to me that the focus should be lightweight and uniformed, rather than having as many features as a modern password manager. -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 61.1...@gmail.com changed: What|Removed |Added CC||61.1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Niklas Sombert changed: What|Removed |Added CC||nik...@ytvwld.de -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 pos...@posteo.eu changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 --- Comment #18 from Alexander Schlarb --- +1 for using KeyPassXC (which is even implemented using Qt5 in case you're wondering) as default provider. It's still lacking libsecret support as well through (https://github.com/keepassxreboot/keepassxc/issues/1403), but doing the work there has the possibility of potentially benefiting a lot more users as Syaid correctly observed. -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 --- Comment #17 from Syiad --- (In reply to Alexander Schlarb from comment #16) > Why not just use `gnome-keyring-daemon` on KDE? I mean as a standard KDE > plasma desktop component not as a every-user-for-himself bolted on top > thing, of course. Why not use 'KeePass' instead and have it integrated into the KDE ecosystem? With people using different platforms (smartphone, tablet, Windows, Linux) on different devices concurrently, it would be smarter to have a credentials storage that works across devices and platforms. A platform-specific solution, even if it works with Gnome _and_ KDE, but only on Linux, is a bit outdated. KeePass is available for all relevant platforms and has thus become a de-facto standard. It also offers the benefit of storing the (endcrypted) credentials database in a cloud storage, such that the same data is available across all devices. -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Alexander Schlarb changed: What|Removed |Added CC||alexander-...@ninetailed.ni ||nja --- Comment #16 from Alexander Schlarb --- Why not just use `gnome-keyring-daemon` on KDE? I mean as a standard KDE plasma desktop component not as a every-user-for-himself bolted on top thing, of course. It comes with no “exciting” dependencies (GIO, GLib, gnuTLS & libcap-ng, as well as GSettings+DConf [some people may object to this, I know] and p11-kit [for smartcards]). Some user-facing utilities (gcr-prompter, gcr-ssh-askpass & pinentry-gnome3) do depend on GTK+3 but these can easily be replaced where this hasn't already happened (pinentry-qt). The biggy left for this approach is of course the frontend (seahorse), but this could be done incrementally: start with a basic “show my passwords” UI, then extend it as users keep asking for other stuff. -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 --- Comment #15 from Yan --- org.freedesktop.secrets Required by microsoft docker vscode extension and most probably Skype, so I wish it will be implemeted soon. -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Yan changed: What|Removed |Added CC||yanp.b...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Kyle Tirak changed: What|Removed |Added CC||lonefen...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 --- Comment #14 from Luis Miguel García Mancebo --- Sorry: failed to say that Kwallet is enabled and opened, yet Remmina keeps printing the same error. Is "secrets" service enabled and working in KWallet? -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Luis Miguel García Mancebo changed: What|Removed |Added CC||kte...@ktecho.com --- Comment #13 from Luis Miguel García Mancebo --- Hey, It's 2018 already :) Can we have some more info on this one? I think this is not working, at least in Kubuntu 18.04 daily. I'm trying the Remmina client and it says this: ** Message: 11:14:16.974: Remote error from secret service: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 boris64 changed: What|Removed |Added CC||bugs@boris64.net -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 --- Comment #12 from Syiad --- Yes - maybe. But it is far from straight forward. I tried to enable it on Kubuntu 15.10 -> no success. Haven't tried with 16.04 yet. Is there a how-to for Kubuntu 16.04 somewhere? -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 --- Comment #11 from Rex Dieter --- kwallet can use login credentials, if you have pam-kwallet installed/enabled -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 Syiad changed: What|Removed |Added CC||syiad.al-d...@web.de --- Comment #10 from Syiad --- kwallet repeatedly asks for the password, e.g. when another program starts. ksecretservice as replacement will hopefully use the login credentials. When can we poor ordinary users have it? It would be great, if you could release a working version and improve it later. User feedback should then help guide your improvement efforts, once we have a chance to actually use it. -- You are receiving this mail because: You are watching all bug changes.
[ksecretsservice] [Bug 313216] Release a working version of KSecretService
https://bugs.kde.org/show_bug.cgi?id=313216 --- Comment #9 from Murz --- Is there any improvements about KSecretService in fresh KDE releases? -- You are receiving this mail because: You are watching all bug changes.
