Bug 363154 - Cannot create certificate with @ in the name field.
Summary: Cannot create certificate with @ in the name field.
Status: RESOLVED WORKSFORME
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: 2.2.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Andre Heinecke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-16 23:46 UTC by Stefan
Modified: 2022-11-20 05:12 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 Stefan 2016-05-16 23:46:16 UTC
Trying to create a new certificate with the @-sign in the name field fails (unless the @ is used as the first character in the name).
Using gpg directly to create a keypair, this works just fine.

Note that in some cases keys are generated specifying the email address as the name and as the email address to ensure privacy where the key is used. For instance the end-to-end-encryption of posteo.de only accepts OpenPGP keys which comply to that restriction: https://posteo.de/en/help/policies-for-public-keys

Reproducible: Always

Steps to Reproduce:
1. File -> New Certificate -> Create a personal OpenPGP key pair
2. Try to enter the following name: foo@bar.com

Actual Results:  
The @-sign cannot be entered. Trying to enter it results in a noop.

Expected Results:  
The @-sign can correctly be entered.
Comment 1 Justin Zobel 2022-10-21 00:17:42 UTC
Thank you for reporting this bug 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 "CONFIRMED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-11-05 05:08:14 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-11-20 05:12:30 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!