[kleopatra] [Bug 325806] New: Kleopatra 2.2.0 can't handle large (16K) RSA keys!
rsa_16384 at byom.de
rsa_16384 at byom.de
Wed Oct 9 12:45:49 BST 2013
https://bugs.kde.org/show_bug.cgi?id=325806
Bug ID: 325806
Summary: Kleopatra 2.2.0 can't handle large (16K) RSA keys!
Classification: Unclassified
Product: kleopatra
Version: 2.2.0
Platform: unspecified
OS: MS Windows
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: general
Assignee: kdepim-bugs at kde.org
Reporter: rsa_16384 at byom.de
CC: mutz at kde.org
After installing the new Gpg4win 2.2.1 (2013-10-07) version, I imported my
previously generated long (16383-bit) RSA secret key into Kleopatra. At first
everything seemed to work fine, but after some hours of frustration I came to
the conclusion that Kleopatra can't handle such large keys. It is possible to
encrypt a file, but not to DECRYPT. Every time after pinentry, Kleopatra
crashes with these details:
APPCRASH
gpg2.exe
2.0.22.8453
libgcrypt-11.dll
(given by Windows 8 Pro - 64 Bit)
Also, with Thunderbird 24.0 and the latest Enigmal v1.6, there is a similar
problem. It is possible to send encrypted emails with the 16K key public key,
but every try to decrypt the message with the private part crashes Enigmail.
It would be a pity if these days only 4096-bit keys would work with Kleopatra.
Any help appreciated.
Reproducible: Always
Steps to Reproduce:
1. Encrypt file/email with 16K key.
2. Try to decrypt it, make pinentry.
3. Crash.
Actual Results:
Kleopatra application crash:
APPCRASH
gpg2.exe
2.0.22.8453
libgcrypt-11.dll
(given by Windows 8 Pro - 64 Bit)
Expected Results:
Accept pinentry, decrypt file/email.
Why large RSA keys might be already necessary:
Post-quantum threats to traditional cryptography and generating 16k RSA
asymmetric key pairs with GnuPG
http://randexec.wordpress.com/2013/07/15/modify-gnupg-to-generate-16k-asymmetric-rsa-key-pairs/
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Kdepim-bugs
mailing list