Bug 390699 - which file is Kgpg's "password-store" and when and how to set a password for it?
Summary: which file is Kgpg's "password-store" and when and how to set a password fo...
Status: RESOLVED DUPLICATE of bug 323392
Alias: None
Product: kgpg
Classification: Applications
Component: general (show other bugs)
Version: 17.12.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Rolf Eike Beer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-18 20:55 UTC by 222.222.ffffffff
Modified: 2018-02-19 13:10 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description 222.222.ffffffff 2018-02-18 20:55:16 UTC
which file is Kgpg's  "password-store"  and when and how to set a password for it?

why do they not use KWALLETMANAGER as one would expect from a KDE app.


upon encryption of a file , I do infact see "another dialog box", asking for password and whether to
store that passwd in a "password-store" - for which another password is required.

so you deal with 2 passwords here, already leading to confusion.

But of course, Kgpg breaks and it is impossible to ever make use of said "password-store". 
And that  password-store is not KWALLETMANAGER, it appears. Cannot be in firefox either.

Then again, it might be, since exactly zero information is given anywhere in KDE about 
exactly which password-store that is, and which it is not. 

The Kgpg manual refers to gpg but about symmetric encryption. But the gpg
people just ignore this foreign reference. Of course, those doing gpg-proper
documentation could not care less about filling the gaping gaps in the GUIs docs.

I looked into the source code but that is tricky.
Comment 1 222.222.ffffffff 2018-02-18 21:01:12 UTC
I talk about symmetrical encryption of a file.
Comment 2 Rolf Eike Beer 2018-02-18 21:10:38 UTC
KGpg has no password store.

*** This bug has been marked as a duplicate of bug 323392 ***
Comment 3 fox 2018-02-19 13:10:40 UTC
call it what you want, mate