https://bugs.kde.org/show_bug.cgi?id=323392
linuxguy changed:
What|Removed |Added
CC|applez...@gmail.com |
--
You are receiving this mail because:
You are wa
https://bugs.kde.org/show_bug.cgi?id=323392
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINF
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #34 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=323392
Justin Zobel changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #32 from f...@ffoxfire.33mail.com ---
to summarize: I cannot see a bug, but documentation is lacking imho.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #31 from f...@ffoxfire.33mail.com ---
even the seahorse GUI does not tell you in which file those passwds ares
stored. Why not? its important to know.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #30 from f...@ffoxfire.33mail.com ---
amazing, how nobody feels the need to document where the heck (i.e. file &
path) those darn passwords are being stored. or is it anywhere on
https://developer.gnome.org/gnome-keyring/stable/ch01.html
-
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #29 from f...@ffoxfire.33mail.com ---
(In reply to Rolf Eike Beer from comment #23)
> That's why the KGpg documentation says
> nothing about it: it's a totally different program that is only a helper
> for gpg, so "far away" in the dependency
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #28 from f...@ffoxfire.33mail.com ---
so to answer my own question: the password will not be stored, i.e. will be
stored nowhere.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #27 from f...@ffoxfire.33mail.com ---
Comment on attachment 110844
--> https://bugs.kde.org/attachment.cgi?id=110844
where is the password stored now? ( using pinentry-qt)
I guess enabling the option will silently be ignored.
--
You are
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #26 from f...@ffoxfire.33mail.com ---
Created attachment 110844
--> https://bugs.kde.org/attachment.cgi?id=110844&action=edit
where is the password stored now? ( using pinentry-qt)
OK I removed package gcr and gnome-keyring. Now indeed pin
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #25 from f...@ffoxfire.33mail.com ---
Created attachment 110843
--> https://bugs.kde.org/attachment.cgi?id=110843&action=edit
more explanatory getpin-qt
a more explanatory getpin-qt tells the user what it wants and were the
password is
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #24 from f...@ffoxfire.33mail.com ---
At least the wiki must reflect the accurate state of affairs, if it deserves to
be called 'wiki'. We're on it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #23 from Rolf Eike Beer ---
I _think_ this is going on: KGpg runs gpg. Gpg starts a pinentry to ask for the
passphrase (gcr in your case). That offers to store the password in a keyring
(the gnome one I think). That's why the KGpg documentat
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #22 from f...@ffoxfire.33mail.com ---
the root cause of the problem is clear: Linux has too few password-stores.
/etc/passwd , firefox has 2, KDEWALLET has x , gpg has 2+
that is not enough ! it is not confusing at all ! we need 5000 passw
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #21 from f...@ffoxfire.33mail.com ---
Created attachment 110806
--> https://bugs.kde.org/attachment.cgi?id=110806&action=edit
how not to program a GUI - keep the user in the dark about all
seemingly the only way to get rid of this problem
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #20 from f...@ffoxfire.33mail.com ---
ah btw, deleting the keyring in ~/gpg/ altogether does not help. of course
not.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #19 from f...@ffoxfire.33mail.com ---
the problematic windows is
/usr/lib/gcr/gcr-prompter
from package gcr . documentation is pretty worthless, as was to be expected.
maybe some stuff in /etc/pam.d/ plays into it. who knows.
--
You ar
https://bugs.kde.org/show_bug.cgi?id=323392
f...@ffoxfire.33mail.com changed:
What|Removed |Added
Attachment #110805|password + passphrase - |password + passphrase -
descri
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #17 from f...@ffoxfire.33mail.com ---
Created attachment 110805
--> https://bugs.kde.org/attachment.cgi?id=110805&action=edit
password + passphrase - where and when has thepassword been set at all?
the lower "password" dialog is the big pr
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #16 from f...@ffoxfire.33mail.com ---
so I thought. after the big ARCH update today, even gpg exhibits the problem.
so gpg and kgpg act the same way. both are buggy. how to set that keyring
password - Ubuntu suggests to delete the whole keyr
https://bugs.kde.org/show_bug.cgi?id=323392
f...@ffoxfire.33mail.com changed:
What|Removed |Added
CC||f...@ffoxfire.33mail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=323392
f...@ffoxfire.33mail.com changed:
What|Removed |Added
CC|f...@ffoxfire.33mail.com |
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #14 from f...@ffoxfire.33mail.com ---
in fact, try this: do a symmetric file encrypt first ith Kleopatra - it will
work as expected, whether or not "save password" is used.
Then do the exact same thing with Kgpg and try "save password in ke
https://bugs.kde.org/show_bug.cgi?id=323392
f...@ffoxfire.33mail.com changed:
What|Removed |Added
CC||f...@ffoxfire.33mail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #12 from 222.222.f...@recursor.net ---
(In reply to Rolf Eike Beer from comment #11)
> *** Bug 390699 has been marked as a duplicate of this bug. ***
in my other report it is ver< obvious how to reproduce the bug. maybe the
problem is us
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #11 from Rolf Eike Beer ---
*** Bug 390699 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=323392
--- Comment #10 from Rolf Eike Beer ---
Please send pictures of these dialogs, and use a user account with English
locale to make tracing easier.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=323392
222.222.f...@recursor.net changed:
What|Removed |Added
CC||222.222.@recursor.n
https://bugs.kde.org/show_bug.cgi?id=323392
222.222.f...@recursor.net changed:
What|Removed |Added
CC|222.222.@recursor.n |
|et
https://bugs.kde.org/show_bug.cgi?id=323392
222.222.f...@recursor.net changed:
What|Removed |Added
CC||222.222.@recursor.n
31 matches
Mail list logo
