https://bugs.kde.org/show_bug.cgi?id=399232
m.k...@irregular.at changed:
What|Removed |Added
CC||m.k...@irregular.at
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=399232
Sam James changed:
What|Removed |Added
CC||s...@gentoo.org
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=399232
Martin changed:
What|Removed |Added
CC||mh...@pm.me
--
You are receiving this mail because:
Y
https://bugs.kde.org/show_bug.cgi?id=399232
--- Comment #15 from Bernd Steinhauser ---
(In reply to michaelk83 from comment #13)
> (In reply to Bernd Steinhauser from comment #11)
> For KeePass, there is a standard file format (`.kdbx`) that multiple
> applications can work with, and indeed there
https://bugs.kde.org/show_bug.cgi?id=399232
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=399232
--- Comment #13 from michaelk83 ---
(In reply to Bernd Steinhauser from comment #11)
For KeePass, there is a standard file format (`.kdbx`) that multiple
applications can work with, and indeed there are many KeePass variations that
all work with this fo
https://bugs.kde.org/show_bug.cgi?id=399232
Borden changed:
What|Removed |Added
CC||i...@bordenrhodes.com
--- Comment #12 from Borden ---
https://bugs.kde.org/show_bug.cgi?id=399232
Bernd Steinhauser changed:
What|Removed |Added
CC||li...@bernd-steinhauser.de
--- Comment #11
https://bugs.kde.org/show_bug.cgi?id=399232
--- Comment #10 from michaelk83 ---
(In reply to michaelk83 from comment #9)
Btw, if KDE devs decide to port KWalletManager to Secret Service before
discontinuing it, *then* it can also act as a front-end for pass, again via the
likes of pass_secret_ser
https://bugs.kde.org/show_bug.cgi?id=399232
--- Comment #9 from michaelk83 ---
(In reply to Borden from comment #8)
At least at the moment, KWallet and pass are two completely separate systems.
They can each present the same Secret Service API to client apps, so the apps
don't care which one is b
https://bugs.kde.org/show_bug.cgi?id=399232
--- Comment #8 from B Rhodes ---
I'm 110% in support of having KWallet be a front-end to a 'proper' OS password
management service. Of the lot, I think Pass is the best candidate because of
its near universal portability across *nix systems, its adheren
https://bugs.kde.org/show_bug.cgi?id=399232
--- Comment #7 from michaelk83 ---
(In reply to Michi from comment #6)
The main goal of this task, as I understand, is to have KDE apps access
passwords from the pass backend. The proposed solution was to integrate pass
with KWallet, and then have the
https://bugs.kde.org/show_bug.cgi?id=399232
--- Comment #6 from Michi ---
(In reply to michaelk83 from comment #5)
> (In reply to michaelk83 from comment #4)
> > What you want here is a separate daemon that exposes the pass backend
> > through the Secret Service API.
> Actually, this already exis
https://bugs.kde.org/show_bug.cgi?id=399232
--- Comment #5 from michaelk83 ---
(In reply to michaelk83 from comment #4)
> What you want here is a separate daemon that exposes the pass backend
> through the Secret Service API.
Actually, this already exists: https://github.com/mdellweg/pass_secret_
https://bugs.kde.org/show_bug.cgi?id=399232
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #4 from michaelk83
https://bugs.kde.org/show_bug.cgi?id=399232
ebray187 changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=399232
Michi changed:
What|Removed |Added
CC||wosk...@yahoo.de
--- Comment #2 from Michi ---
I have
https://bugs.kde.org/show_bug.cgi?id=399232
Silver Salonen changed:
What|Removed |Added
CC||silver.salo...@gmail.com
--- Comment #1 from S
18 matches
Mail list logo
