Bug 396300 - account assistant creates pgp key without asking when gpg-agent is running
Summary: account assistant creates pgp key without asking when gpg-agent is running
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 5.8.2
Platform: FreeBSD Ports FreeBSD
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-08 01:52 UTC by Jonathan M Davis
Modified: 2022-12-26 05:21 UTC (History)
0 users

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 Jonathan M Davis 2018-07-08 01:52:42 UTC
When creating a new account in kmail, on the "Secure your Communication" page of the wizard, it not only defaults to "Secure outgoing emails, if possible," but it outright creates a PGP key and adds it to my wallet. It's one thing for it to want to do gpg by default (which I disagree with), but it's another thing entirely to create a key without even asking me first. This means that when I add an account, I have go and delete unwanted PGP keys from my wallet.

From what I can tell after some experimenting, kmail only creates the key if gpg-agent is running. I guess that kmail assumes that I want to use gpg for e-mail just because I have gpg-agent running, but regardless, I really don't think that it's appropriate for kmail to be creating PGP keys without even asking first. Even if I did want to use gpg with kmail right now, I wouldn't want it to create keys without asking first.
Comment 1 Justin Zobel 2022-11-26 00:13:51 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-12-11 05:07:57 UTC
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 bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-12-26 05:21:52 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!