https://bugs.kde.org/show_bug.cgi?id=363154
Bug ID: 363154 Summary: Cannot create certificate with @ in the name field. Product: kleopatra Version: 2.2.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: aheine...@intevation.de Reporter: luke1...@gmx.de CC: kdepim-bugs@kde.org, m...@kde.org 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: f...@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. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs