[kaddressbook] [Bug 356453] New: only valid (signed) openpgp certificates (keys) can be assigned
https://bugs.kde.org/show_bug.cgi?id=356453 Bug ID: 356453 Summary: only valid (signed) openpgp certificates (keys) can be assigned Product: kaddressbook Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ha...@laging.de CC: to...@kde.org OpenPGP certificates have several levels of validity: They can be invalid (expired, revoked, locally disabled), neutral and marginally or fully valid. Certificates become valid by assinging ultimate trust (which should be limited to one's own keys) or by being signed by one ore more keys with trust privilege. It is perfectly OK to use neutral / non-valid certificates. KMail does allow you to do that (with a warning; as it should be). You can assign certificates to a contact (assigning to an email address would make more sense, though). The problem is that the key selection dialog allows you to select valid certificates only which doesn't make sense. If you encrypt to an email address which does not appear in any certificate then the same dialog appears (within KMail, not within KAddressbook) and then it does allow you to select a non-valid certificate... Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 350969] New: KMail does not reopen windows on different virtual desktops
https://bugs.kde.org/show_bug.cgi?id=350969 Bug ID: 350969 Summary: KMail does not reopen windows on different virtual desktops Product: kmail2 Version: 4.14.7 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: ha...@laging.de If KMail is closed or crashes then it restores the message windows which were open in that moment. This is an extremely useful feature. Because I often have so many message windows open (those which I have to reply to) that I easily lose track, I have put some of those windows on the next virtual desktop. These windows are not restored after quitting and restarting KMail. The behaviour is the same if the system crashes. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 294673] Cannot open messages forwarded as attachment (shown as empty)
https://bugs.kde.org/show_bug.cgi?id=294673 Hauke Laging ha...@laging.de changed: What|Removed |Added CC||ha...@laging.de --- Comment #10 from Hauke Laging ha...@laging.de --- If this has been fixed then there has been a regression afterwards. This problem occurs in 4.14.8 (and I have noticed it for quite some time but don't know the version when it started). -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 340602] KMail puts PGP/MIME signed attachments twice into the same mail (doubling mailsize)
https://bugs.kde.org/show_bug.cgi?id=340602 --- Comment #4 from Hauke Laging ha...@laging.de --- I confirm this for 4.14.8 But not only are the attachments added twice to the mail but the mail body, too. Of course, due to the typical size relation this is not obvious. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 340602] KMail puts PGP/MIME signed attachments twice into the same mail (doubling mailsize)
https://bugs.kde.org/show_bug.cgi?id=340602 Hauke Laging ha...@laging.de changed: What|Removed |Added CC||ha...@laging.de --- Comment #3 from Hauke Laging ha...@laging.de --- Created attachment 93289 -- https://bugs.kde.org/attachment.cgi?id=93289action=edit test mail (mbox file) This is a very small email for demonstration purposes. The attachments are two one-line plain/text files. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 318005] promote OpenPGP (and S/MIME) services for non-crypto users
https://bugs.kde.org/show_bug.cgi?id=318005 Hauke Laging ha...@laging.de changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Hauke Laging ha...@laging.de --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 348951] New: show and check (and compare) the timestamp of the signature(s)
https://bugs.kde.org/show_bug.cgi?id=348951 Bug ID: 348951 Summary: show and check (and compare) the timestamp of the signature(s) Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: ha...@laging.de KMail shows the verification result of a signature but it does not show the signature timestamp. It does not even show this information in the details. Enigmail shows this important information by default. Much better than showing this value by default would be to compare it to the non-crypto date mail header. If they differ by more than a few seconds then a warning should be shown. Another point: I have to admit that I didn't check this yet. But in case of PGP/Inline mails the timestamp and key ID of the body signature should be compared to those of the attachments. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 348952] New: show the OpenPGP format (PGP/MIME vs. PGP/Inline)
https://bugs.kde.org/show_bug.cgi?id=348952 Bug ID: 348952 Summary: show the OpenPGP format (PGP/MIME vs. PGP/Inline) Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: ha...@laging.de It makes a big difference for signatures (both encrypted and unencrypted) whether an email is in PGP/Inline or PGP/MIME format. The reason is that you can delete attachments from a PGP/Inline email without breaking the signatures. For experts it's just a short look at the message source code but that's obviously not an option for the general public. The message signed by foo@bar should be replaced by e.g. PGP/Inline message signed by foo@bar. It would be nice to show a short explanation if the problem to the user if he clicks on PGP/Inline or PGP/MIME. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 345968] New: make main window easier to find in window list
https://bugs.kde.org/show_bug.cgi?id=345968 Bug ID: 345968 Summary: make main window easier to find in window list Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: ha...@laging.de I often have a lot of open emails. Although I have a separate window list I cannot immediately see which entry I have to click to get the main window in the foreground. For some reason the main window is not the first entry but somewhere in the middle. The second part of the problem is that the main window entry uses the same icon like the message window entries. So I have to read the text of several list entries every time I need the main window. This is annoying. The more as the text of this entry changes. It is not enough to look for KMail because the text is the currently active folder. This could be solved by e.g. making the main window always the first entry (I don't know whether this is a KMail problem or one of the window list) or by using a different icon for this entry. If both cannot be done in KMail then it would help to make KMail not the last but the first part of the window title. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 288141] Kontact crash on exit
https://bugs.kde.org/show_bug.cgi?id=288141 Hauke Laging ha...@laging.de changed: What|Removed |Added CC||ha...@laging.de --- Comment #32 from Hauke Laging ha...@laging.de --- I have probably the same problem – for years now. kontact crashes when exiting (probably due to kmail). This is annoying because the IMAP folder settings (like when to check for new mail) are not saved. Open mail creating windows are restored, though. After my upgrade from openSUSE 13.1 to 13.2 kmail was completely broken so I deleted the whole akonadi database and created the kmail IMAP accounts again. To my surprise some of the other configuration (like the identities) was still there. I am also surprised that kmail still crashes. So it seems not related to the IMAP stuff. I must admit though that I didn't think of closing kmail before adding the IMAP accounts just for crash testing. This is the crash data I get: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7fd7128ae800 (LWP 3267))] Thread 4 (Thread 0x7fd6f522b700 (LWP 3268)): #0 0x7fd709ec105f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd70d652686 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x7fd70d6526b9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7fd709ebd0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7fd70fe307fd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fd6b4910700 (LWP 3269)): #0 0x7fd709ec105f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd70d3c4e7d in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib64/libQtWebKit.so.4 #2 0x7fd70d67a1e6 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7fd709ebd0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7fd70fe307fd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fd6a4a9d700 (LWP 3288)): #0 0x7fd70fe2449d in read () from /lib64/libc.so.6 #1 0x7fd709932750 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fd7098f1714 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fd7098f1b7b in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fd7098f1cec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fd7105ab0de in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #6 0x7fd71057ce6f in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #7 0x7fd71057d165 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #8 0x7fd71047a0bf in QThread::exec() () from /usr/lib64/libQtCore.so.4 #9 0x7fd71047c79f in ?? () from /usr/lib64/libQtCore.so.4 #10 0x7fd709ebd0a4 in start_thread () from /lib64/libpthread.so.0 #11 0x7fd70fe307fd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fd7128ae800 (LWP 3267)): [KCrash Handler] #5 0x7fd711a35bd0 in vtable for QPaintDevice () from /usr/lib64/libQtGui.so.4 #6 0x0040382f in ?? () #7 0x7fd70fd6cb05 in __libc_start_main () from /lib64/libc.so.6 #8 0x00403c97 in _start () -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 288141] Kontact crash on exit
https://bugs.kde.org/show_bug.cgi?id=288141 --- Comment #33 from Hauke Laging ha...@laging.de --- I have to correct and extend my last posting: In contrast to earlier experiences the folder settings are saved now despite of the crash. The problem is kmail related in a strange way: If I deactivate kmail in kontact then kontact does not crash any more on exit. But the really weird thing is: If I start kmail alone (not via kontact) then it doesn't crash on exit... So the work-around seems to be to run kontact and kmail in parallel. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 120392] GUI for enabling/disabling of signature and encryption is confusing
https://bugs.kde.org/show_bug.cgi?id=120392 --- Comment #5 from Hauke Laging ha...@laging.de --- It's worth noting that Enigmail does that meanwhile. At least partly. They do not show correctly what is going to happen with an email but they show that the default setting has been changed. And if it is changed back to its original value then this value overrides the (non-shown) settings for the recipient. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 340124] New: contact crypto settings are selected not only by email address but also by name
https://bugs.kde.org/show_bug.cgi?id=340124 Bug ID: 340124 Summary: contact crypto settings are selected not only by email address but also by name Product: kmail2 Version: 4.11.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: ha...@laging.de I have a contact with the crypto setting always encrypt which consists of an email address and a first name. Now I recieved an email from someone who also has just his first name in the from address. And it is the same name. I replied to this email. The bug is that KMail applies the crypto settings of a different person to this email. It encrypts the email with the key of someone else. If I try to prevent that in the these keys are going to be used dialog then I have to create an address book entry. If I don't do that then the email is sent encryptedly. If the second person has its own address book entry then this problem does not occur. To make it worse: I just deleted the address book entry for the second address and replied to the email again (for testing). This time the email was sent unencryptedly (the key dialog did not appear either). Reproducible: Sometimes -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 339360] New: offline accounts should try to reconnect automatically
https://bugs.kde.org/show_bug.cgi?id=339360 Bug ID: 339360 Summary: offline accounts should try to reconnect automatically Product: kmail2 Version: 4.11.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ha...@laging.de If there is a connection problem with the IMAP server (maybe the same with POP3) then KMail switches the respective account to offline mode. But there is no obvious hint for this change. You have to click on the folders belonging to this account to notice the change. This can be quite annoying if there are many accounts and the affected one is not important. I often miss mails for several days because I am not aware that a certain mailbox (with low traffic and usually not so important messages) is offline. The solution is obvious and very easy to implement: If an account is switched to offline then KMail should automatically try to reconnect after a reasonable time, say every hour. An alternative or parallel reaction (very easy to implement, too) would be to add an optical hint e.g. change the folder icon to red or add a new element above the folder list. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 339360] offline accounts should try to reconnect automatically
https://bugs.kde.org/show_bug.cgi?id=339360 --- Comment #1 from Hauke Laging ha...@laging.de --- I forgot to mention that there is a similar bug entry: https://bugs.kde.org/show_bug.cgi?id=332652 But the described behaviour is not a bug IMHO. And the proposed solution seems a bit simple. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 339087] you cannot encrypt to an expired OpenPGP certificate
https://bugs.kde.org/show_bug.cgi?id=339087 Hauke Laging ha...@laging.de changed: What|Removed |Added Severity|major |wishlist -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 339087] you cannot encrypt to an expired OpenPGP certificate
https://bugs.kde.org/show_bug.cgi?id=339087 --- Comment #1 from Hauke Laging ha...@laging.de --- I have to suspend this bug report as it turned out that this is a problem of the underlying GnuPG (at least gpg) which currently does not allow this. Maybe this will be changed in future versions. But I don't know whether this problem affects gpgme, though. http://lists.gnupg.org/pipermail/gnupg-users/2014-September/050850.html There is no concensus in the community what is the right behaviour. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 339087] New: you cannot encrypt to an expired OpenPGP certificate
https://bugs.kde.org/show_bug.cgi?id=339087 Bug ID: 339087 Summary: you cannot encrypt to an expired OpenPGP certificate Product: kmail2 Version: 4.11.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: ha...@laging.de KMail does not allow to encrypt to expired certificates. It is OK to warn about that (and would be a failure not to do so) but not allowing to encrypt to this key is a severe security failure because it does not make any sense and forces the user to use a different key (if available, usually not) or to send the mail unencrypted. This is similar to the old (meanwhile solved) problem that you could not encrypt to non-valid keys. Of course, encrypting to a non-valid (i.e. never has been valid) key is much more severe that encrypting to an expired one which a purely formal problem not a technical one. Reproducible: Always Steps to Reproduce: 1. Let a certificate expire. 2. Try to send a mail encrypted to this certificate. Actual Results: Email cannot be sent. Expected Results: Warning which can be overridden. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 318005] promote OpenPGP (and S/MIME) services for non-crypto users
https://bugs.kde.org/show_bug.cgi?id=318005 --- Comment #3 from Hauke Laging ha...@laging.de --- After creating this entry the Cryptoparty community https://www.cryptoparty.in/ became quite big and well known. Thus this would probably be the main hint for the users. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 337617] New: add symmetric OpenPGP email encryption
https://bugs.kde.org/show_bug.cgi?id=337617 Bug ID: 337617 Summary: add symmetric OpenPGP email encryption Product: kmail2 Version: 4.10.5 Hardware: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: ha...@laging.de OpenPGP is typically used with asymmetric encryption (key pairs) but the standard contains a definition for symmetric (but still two level) encryption. With gpg this is done by using --symmetric instead of --encrypt. KMail, Thunderbird/Enigmail and more clients can already decrypt emails which have been encrypted symmetrically. This can be tested with this file: http://www.crypto-fuer-alle.de/docs/mail-symmetric/mail.cr-lf.eml I suggest to add the capability to symmetrically encrypt mails to KMail. Symmetric encryption can be more easily used than asymmetric encryption if none has been prepared yet. For symmetric encryption the necessary software just has to be installed but not configured. People are familiar with passwords but not with key pairs. In the case of KMail nothing would have to be done as GnuPG is always installed. It doesn't make any sense at all to force the users to use something different from OpenPGP when they want to use symmetric encryption. This is not supposed to be an alternative to regular OpenPGP usage but an alternative for those who are not willing or not capable to prepare for the use of key pairs in that moment. Most people would not use this feature permanently. If they start encrypting emails regularly they will probably switch to typical OpenPGP usage. This feature should be very easy to implement. There has been a long discussion on the GnuPG mailing list: http://lists.gnupg.org/pipermail/gnupg-users/2014-July/050281.html -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 322708] kmail should allow encrypting mails with keys of unknown/zero trust
https://bugs.kde.org/show_bug.cgi?id=322708 --- Comment #4 from Hauke Laging ha...@laging.de --- (In reply to comment #3) I understand the bug in that way, that I got a private key which I'm not fully trusting. Private keys are neither valid nor trusted. Certificates (public keys) are (in)valid and (un)trusted. Nevertheless KMail shouldn't deny to use the key but give a clear warning. Indeed. I can manually select a key for which I set the trust-level to anything less then Ultimately (using Kgpg) for signing but I CAN'T select it for encryption. GnuPG doesn't care about the trust level but about the validity level. The trust level doesn't change the validity level (exception: ultimate). You should never use ultimate trust in order to make a key valid. If I set a full-trusted key as default for a KMail identity You mean ultimately trusted? This is important! If someone forgot to create a new key or to send me a new key I should be able so send him an encrypted email asking for that! And it must be possible to encrypt to an invalid key because otherwise the user is forced to pretend a key validation (unless he knows certain tricks). -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 328770] I'm not able to encrypt a mail with a key which has a different email address.
https://bugs.kde.org/show_bug.cgi?id=328770 --- Comment #3 from Hauke Laging ha...@laging.de --- (In reply to comment #2) Steps to Reproduce: 1. Create a mail to foo...@example.net 2. Try to encrypt it with a valid pgp key of someone else What happens if you try this in a shell? echo foo | gpg --armor --recipient wu...@example.net --encrypt -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 328770] I'm not able to encrypt a mail with a key which has a different email address.
https://bugs.kde.org/show_bug.cgi?id=328770 --- Comment #5 from Hauke Laging ha...@laging.de --- (In reply to comment #4) The problem is I have a key for a...@redhat.com but send a mail to ansch...@redhat.com. The person is the same and I want to encrypt the mail using the key for a...@redhat.com but kmail doesn't allow me to do that. Unfortunately you still haven't given the KMail version you are using. I just did a better test: I wrote an email to an address which doesn't have a certificate. There was a warning and I was given a dialog from which I could select a key and then everything was fine. So your KMail version may have a bug but it seems that it has been fixed meanwhile so this bug report should be closed. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 328770] I'm not able to encrypt a mail with a key which has a different email address.
https://bugs.kde.org/show_bug.cgi?id=328770 Hauke Laging ha...@laging.de changed: What|Removed |Added CC||ha...@laging.de --- Comment #1 from Hauke Laging ha...@laging.de --- You have to improve your bug report: The headline is not consistent with the text. The headline says you cannot encrypt, the text says you cannot sign. The reproduction steps do not even make sense: Try to sign it with a valid pgp key of someone else You cannot sign with someone else's key. (Yours are those keys for which you have the secret part.) I have 4.10.5 and I can both encrypt to another key and sign with another key (which requires changing the identity configuration though). So either this was a bug which has already been fixed (or a regression which came up in a version newer than mine) or you are doing something wrong. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 327986] when I GnuPG encrypt to several receivers and I have more than one of the receiving keys myself, I am asked multiple times for my password
https://bugs.kde.org/show_bug.cgi?id=327986 Hauke Laging ha...@laging.de changed: What|Removed |Added CC||ha...@laging.de --- Comment #2 from Hauke Laging ha...@laging.de --- (In reply to comment #0) When I now click on one of my sent mails (or receive one of the mails - I always BCC myself) I have to enter multiple passwords: at least one for each key. Are that more than two keys and are you sure that you are asked the passphrase for different keys (check the pinentry message!)? Are you sure this is different from the bug you reported two weeks earlier? https://bugs.kde.org/show_bug.cgi?id=327357 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 327986] when I GnuPG encrypt to several receivers and I have more than one of the receiving keys myself, I am asked multiple times for my password
https://bugs.kde.org/show_bug.cgi?id=327986 --- Comment #3 from Hauke Laging ha...@laging.de --- (In reply to comment #0) at least one for each key. Once for each of your keys or once for every target key? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 327986] when I GnuPG encrypt to several receivers and I have more than one of the receiving keys myself, I am asked multiple times for my password
https://bugs.kde.org/show_bug.cgi?id=327986 --- Comment #4 from Hauke Laging ha...@laging.de --- (In reply to comment #1) If you don't see your keyid at the output, gpg has to test all keys. That doesn't make sense if his description is precise: If he hides the IDs of n recipient keys and at least two of them are his own (which are probably the last in the list) then he should have to try n-1 keys only because every key of his own could decrypt the message. Perhaps it helps to save the mail to a file, attach strace -p $PID -f -e trace=execve to the kmail/kontact process (in order to see the gpg calls) and then open the file. Perhaps it makes sense to add some gpg debugging capability to KMail. If it is activated all gpg calls and a copy of all used data are written to a directory. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 322708] kmail should allow encrypting mails with keys of unknown/zero trust
https://bugs.kde.org/show_bug.cgi?id=322708 Hauke Laging ha...@laging.de changed: What|Removed |Added CC||ha...@laging.de --- Comment #2 from Hauke Laging ha...@laging.de --- (In reply to comment #0) however it doesn't. This is wrong because encryption is meant to provide confidentiality and the act of signing keys and creating a web of trust is meant to provide authenticity. I can confirm the problem but your explanation doesn't make sense. You seem to not have understood how crypto works. See: http://www.openpgp-schulungen.de/kurzinfo/irrtuemer/#import-ausreichend You need verify the certificate in order to be sure that you encrypt to the right key. Encrypting to the MitM key is not part of the concept confidentiality. Signing keys makes them valid. You need valid keys both for serious encryption and for serious signature checking. Nonetheless this must be fixed because the user must be free to decide to use the key anyway and it is really evil to force the user to certify the key first (or even worse: set it to ultimate trust). -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 324963] general error on sending GPG encrypted mail after telling KMail to use untrusted key
https://bugs.kde.org/show_bug.cgi?id=324963 Hauke Laging ha...@laging.de changed: What|Removed |Added CC||ha...@laging.de --- Comment #1 from Hauke Laging ha...@laging.de --- I can confirm this bug. (KMail 4.10.5) -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 209319] GnuPG: automatically attach my public key and the public key from all receivers - also automatically import attached public keys (decentral key management)
https://bugs.kde.org/show_bug.cgi?id=209319 Hauke Laging ha...@laging.de changed: What|Removed |Added CC||ha...@laging.de --- Comment #4 from Hauke Laging ha...@laging.de --- (In reply to comment #0) I'd love to be able to tell KMail to automatically attach my public GnuPG key and all public GnuPG keys of the receivers to each email I send (and sign/encrypt). In other words: If I get 100 emails from you then I get 100 copies of your certificate, making the search for emails with an attachment completely useless? Are you serious about that, do you want to get rid of your friends...? And you are aware that only the key owner should change public versions of his certificate? Maybe he doesn't want your certification to be seen on his key. Of course, you can avoid this problem with some above average crypto knowledge... Along with the option to automatically import any attached GnuPG key, that would open the possiblity of using GnuPG without the need for central keyservers: If I sign a key, its owner will automatically get the updated version once he gets an email from me. Why not act like the rest of the world and send the certificate to the key owner immediately after creating it? 99% of the users don't care about this problem. The 1% can send you a mail and ask for the others' certificates. The problem you mention does exist but has to be solved at another layer. This will probably be done by moving the responsibility for keyservers to the mail server owner (who knows that you send the mail anyway). -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 305171] PGP/MIME signatures are invalid when text/plain; charset=us-ascii is used
https://bugs.kde.org/show_bug.cgi?id=305171 Hauke Laging ha...@laging.de changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #8 from Hauke Laging ha...@laging.de --- Has been fixed (I don't know in which version, though). -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 329546] New: open validly signed emails only
https://bugs.kde.org/show_bug.cgi?id=329546 Bug ID: 329546 Summary: open validly signed emails only Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: openSUSE RPMs URL: http://www.crypto-fuer-alle.de/wishlist/securitylevel/ OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: ha...@laging.de Email is an important attack vector. Now in the post-Snowden era that we all are discussing how to make computers more secure I think it's time to make crypto more useful. On high security level systems it should be possible to disable the handling of such emails completely (OK except for showing the header data which isn't signed anyway) which do not have a valid PGP/MIME signature by a key which has been explicitly marked trustworthy for this security level (no matter if the email is encrypted or not). This may be done by creating a separate keyring and call gpg with --no-default-keyring or by checking the normal gpg result against a fingerprint whitelist. Instead of the mail content a message like The KMail configuration requires all emails to be signed by a key from the secure keys list. This email is not opened because it lacks a valid signature / has a correct signature but from a key which is not on the secure keys list. Such a configuration probably makes sense only as a global option. But it may make sense to have a secure keys list per mailbox. This may be a nice feature from the admin perspective (even more if the user cannot disable it and cannot modify the secure keys list) because it limits the users possibilities to make mistakes. These signatures could also be made by antivirus software so this feature could as a side effect ensure that only such email is read which has been checked. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 318005] promote OpenPGP (and S/MIME) services for non-crypto users
https://bugs.kde.org/show_bug.cgi?id=318005 --- Comment #2 from Hauke Laging ha...@laging.de --- See this similar proposal: https://bugs.kde.org/show_bug.cgi?id=326476 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 326476] New: add a request for advocating crypto to the crypto configuration
https://bugs.kde.org/show_bug.cgi?id=326476 Bug ID: 326476 Summary: add a request for advocating crypto to the crypto configuration Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: unspecified URL: http://userbase.kde.org/Concepts/OpenPGP_Help_Spread OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: ha...@laging.de We need everyone we can get for help in advocating the usage of crypto tools. Currently even most crypto users are not aware of the opportunities they have for doing that (even at nearly no effort). Thus the crypto configuration windows should get a link to a page which tells them, e.g. the userbase wiki page I created for this purpose: http://userbase.kde.org/Concepts/OpenPGP_Help_Spread (which would solve the translation problem for KMail) See this similar wishlist entry: https://bugs.kde.org/show_bug.cgi?id=318005 Those who understand German may have a look ta my crypto advocationg site (which contains similar ideas), too: http://www.crypto-fuer-alle.de/ Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 322138] New: replying to an encrypted PGP/Inline mail quotes the encrypted data
https://bugs.kde.org/show_bug.cgi?id=322138 Bug ID: 322138 Summary: replying to an encrypted PGP/Inline mail quotes the encrypted data Classification: Unclassified Product: kmail2 Version: 4.10.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: ha...@laging.de If you reply to an encrypted email which is in PGP/Inline format then the new message does not contain the shown cleartext as quote but the PGP/Inline encrypted data. There is an easy workaround (but you have to know the possibility; thus I have not marked this bug as minor): If you mark the cleartext before replying then the cleartext is quoted. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 315726] KMail 2 doesn't accept subkeys for signing and encrypting
https://bugs.kde.org/show_bug.cgi?id=315726 Hauke Laging ha...@laging.de changed: What|Removed |Added CC||ha...@laging.de --- Comment #1 from Hauke Laging ha...@laging.de --- If there is a subkey available for a certain operation then the mainkey is never used. Have a look at the results with gpg --list-packets. You will most probably see that the subkeys have been used. If there are several equivalent subkeys available then you are in the situation that you cannot choose. But this is a seldom, rather complicated operation and probably not your problem. It would be nice, though, if KMail could be configured to use a separate GnuPG configuration. This is possible for KGpg. But that would solve only half of your problem and would not be a very clean solution. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 318005] promote OpenPGP (and S/MIME) services for non-crypto users
https://bugs.kde.org/show_bug.cgi?id=318005 --- Comment #1 from Hauke Laging ha...@laging.de --- Now there is an article in the KDE userbase wiki (in English and German) which could be pointed at by KMail: http://userbase.kde.org/KMail/Courses_Information_Openpgp As an addition to this article I wrote an comprehensive explanation of the OpenPGP concepts (not KMail-specific) for beginners and another one about good key generation; one for advanced users is to follow. Thus the userbase wiki has now become a good resource for OpenPGP beginners. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 305171] PGP/MIME signatures are invalid when text/plain; charset=us-ascii is used
https://bugs.kde.org/show_bug.cgi?id=305171 --- Comment #6 from Hauke Laging ha...@laging.de --- Created attachment 78849 -- https://bugs.kde.org/attachment.cgi?id=78849action=edit mail with bad signature, saved from Thunderbird to a file For reproducing the bug. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 305171] PGP/MIME signatures are invalid when text/plain; charset=us-ascii is used
https://bugs.kde.org/show_bug.cgi?id=305171 --- Comment #7 from Hauke Laging ha...@laging.de --- (In reply to comment #5) Can you give a text, that you entered into kmail, that has an invalid signature? I attach a mail I sent which is shown as badly signed in Thunderbird. Can you pease give kmail 4.10.2 a try? There are some improments with CTE entered kmail. I just noticed that it seems to work in KMail/4.8.5 already. At least it's shown correctly by Thunderbird/Enigmail (which shows older mails as badly signed). -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 318005] New: promote OpenPGP (and S/MIME) services for non-crypto users
https://bugs.kde.org/show_bug.cgi?id=318005 Bug ID: 318005 Summary: promote OpenPGP (and S/MIME) services for non-crypto users Classification: Unclassified Product: kmail2 Version: unspecified Platform: Other URL: http://www.openpgp-schulungen.de/ OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: ha...@laging.de Hardly anyone uses crypto. I assume that nearly everyone who is involved in the development of crypto software would like this to change. My experience is that quite few people decide completely by themselves to have a look at this topic. I guess that the big majority of users has been contacted by others about this and has been offered help. For a few months I have been working on a non-commercial project (up to now limited to Germany though) which aims at creating more free OpenPGP courses and offer a list of these services to the public. The project web site is http://www.openpgp-schulungen.de/ (German only). My idea is that crypto-capable (but non-crypto-specific) software like KMail should advertise such projects if it detects that it is configured for a country in which one exists (I don't know of any similar project abroad yet) and that OpenPGP is not used yet (and S/MIME neither). This could be done by an additional menu entry OpenPGP or crypto which would just open a dialog window with some short remarks about the OpenPGP support in KMail and the link to the local project (and a link to a list of all these projects). Until now I have been much more successful in improving my own OpenPGP course than in helping creating such offers elsewhere but this is the second step anyway and I am optimistic about that. And given the time wishlist entries usually take to get done I think it's not a mistake to mention this here now. ;-) I will present this project at the next LinuxTag in Berlin (at the booth of the Berlin LUG). Furthermore: Given the amout of German KDE developers I guess there is a certain chance that one or the other is interested in supporting this project (or doing something similar in another country) though this is not about programming (except for some scripting which I do myself). Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 305171] PGP/MIME signatures are invalid when text/plain; charset=us-ascii is used
https://bugs.kde.org/show_bug.cgi?id=305171 Hauke Laging ha...@laging.de changed: What|Removed |Added Version|unspecified |4.7 --- Comment #4 from Hauke Laging ha...@laging.de --- (In reply to comment #3) Hauke: which exact Kmail version is this about? Please set the version field. It is 4.7.2 (the current openSUSE version). Now I can set 4.7. Funny, IIRC that value was not available when I opened the bug. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 128454] if copies of sent messages cannot be uploaded to the IMAP server they should be moved there from the local folder later
https://bugs.kde.org/show_bug.cgi?id=128454 --- Comment #4 from Hauke Laging ha...@laging.de --- (In reply to comment #3) Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2. Still valid. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 128453] protect privacy by sending receipts (MDN) after a random delay
https://bugs.kde.org/show_bug.cgi?id=128453 --- Comment #3 from Hauke Laging ha...@laging.de --- (In reply to comment #2) Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2. Still valid. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 120392] GUI for enabling/disabling of signature and encryption is confusing
https://bugs.kde.org/show_bug.cgi?id=120392 --- Comment #3 from Hauke Laging ha...@laging.de --- (In reply to comment #2) Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2. Still valid. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 115062] more control over message disposition notifications
https://bugs.kde.org/show_bug.cgi?id=115062 --- Comment #4 from Hauke Laging ha...@laging.de --- (In reply to comment #3) Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2. Still valid. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 94114] posibility to encrypt received unencrypted emails
https://bugs.kde.org/show_bug.cgi?id=94114 --- Comment #7 from Hauke Laging ha...@laging.de --- (In reply to comment #6) Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2. Still valid. And I would like to extend this feature wish by something that is technically very close: Keys get revoked. And of course, you never know when. The moment a key is revoked all its signatures become worthless – unless you can prove (or be sure if it's for yourself only) that the signature was made (long enough) before the revocation. The protection if IMAP accounts is many orders of magnitude weaker than that of crypto. Thus it would be nice if KMail was able of signing incoming emails. Technically it is AFAIK not possible to sign an already signed email without breaking the message format but instead an additional IMAP mailbox could be created where no email format messages are stored but simply the detached signatures of the normal emails. Those signature files could be named by the message IDs or by the hash values of the emails (or just of the signed part). The last step to happiness would be to prepare for further handling of these signatures by the option to deliver them locally to some program / script (which may request a crypto timestamp from a third party in order to be able to really prove that the signature is valid in case it gets revoked later). -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 305171] nearly all openpgp signatures are invalid
https://bugs.kde.org/show_bug.cgi?id=305171 --- Comment #2 from Hauke Laging ha...@laging.de --- Embarrassing... but I have to correct some of my statements and guesses. Meanwhile I have found the difference between the emails with valid signatures and those with invalid ones: Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset=us-ascii That's the problem. All emails with this encoding have invalid signatures. The problem has nothing to do with the newlines. The sometimes missing newlines between the text signature and the MIME seperator are due to different identities I used for composing the emails. Of the two text signatures of those identities only one had a trailing newline. This effect was due to the change from KMail to KMail2 (because KMail2 killed the KMail configuration and I forgot the newline when restoring the identities manually). Both identities (with and without trailing newline) can create valid and invalid signatures. That just depends on it whether non-ASCII characters occur in the message. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 305171] PGP/MIME signatures are invalid when text/plain; charset=us-ascii is used
https://bugs.kde.org/show_bug.cgi?id=305171 Hauke Laging ha...@laging.de changed: What|Removed |Added Summary|nearly all openpgp |PGP/MIME signatures are |signatures are invalid |invalid when text/plain; ||charset=us-ascii is used -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 305171] New: nearly all openpgp signatures are invalid
https://bugs.kde.org/show_bug.cgi?id=305171 Bug ID: 305171 Severity: major Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: nearly all openpgp signatures are invalid Classification: Unclassified OS: Linux Reporter: ha...@laging.de Hardware: openSUSE RPMs Status: UNCONFIRMED Component: crypto Product: kmail2 Since KMail2 nearly all (more than 90%) of my email signatures are shown as invalid by other mail clients. I tried to understand which software is buggy by reading the rfc but I am still not sure. Most probably it is KMail2. KMail2 shows these signatures as correct. The problem seems to be a missing newline. The MIME seperator is placed directly after my last signature line: PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814 --nextPart20694277.1dnrQtI15C In earlier versions of KMail (and in Thunderbird) there was en empty line in between: PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814 --nextPart3343035.S6mqRQsH14 The signature is not completely wrong. If I save the mail as a file, convert it to DOS newline and add a newline to the end of the data block then I can verify the signature by gpg. So it is obvously just a formatting problem. It seems not to make a difference whether the signature text ends with a newline. Reproducible: Always Steps to Reproduce: 1. Just send a signed email in PGP/MIME format. Actual Results: Signature is not recognized by other mail clients. Expected Results: A compatible signature (or rather: compatible MIME formatting of it). -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 303305] New: A From at the beginning of a line is not escaped thus breaking signatures (ignoring RfC 4880 recommendation)
https://bugs.kde.org/show_bug.cgi?id=303305 Bug ID: 303305 Severity: major Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: A From at the beginning of a line is not escaped thus breaking signatures (ignoring RfC 4880 recommendation) Classification: Unclassified OS: Linux Reporter: ha...@laging.de Hardware: openSUSE RPMs Status: UNCONFIRMED Component: crypto Product: kmail2 KMail (4.7.2 but I haven't found a bug referring to this) violates a RfC 4880 recommendation: # Note: If any line begins with the string From , it is strongly suggested that either the Quoted-Printable or Base64 MIME encoding be applied. If Quoted-Printable is used, at least one of the characters in the string should be encoded using the hexadecimal coding rule. This is because many mail transfer and delivery agents treat From (the word from followed immediately by a space character) as the start of a new message and thus insert a right angle-bracket () in front of any line beginning with From to distinguish this case, invalidating the signature. # This is not really a problem of the crypto component but the failure probably affects crypto only. Reproducible: Always Steps to Reproduce: 1. Write an email with a line beginning with From which is not sent as base64. Actual Results: From is not escaped. Expected Results: As said in the RfC quote. To see the broken signature just send the mail to a suitable mailing list (like the GnuPG mailing list, Mailman version 2.1.12rc1). Local storage in mbox format may work, too. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 303305] A From at the beginning of a line is not escaped thus breaking signatures (ignoring RfC 4880 recommendation)
https://bugs.kde.org/show_bug.cgi?id=303305 --- Comment #2 from Hauke Laging ha...@laging.de --- Created attachment 72429 -- https://bugs.kde.org/attachment.cgi?id=72429action=edit Screenshot of the KMail window with the non-validating signature -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 303305] A From at the beginning of a line is not escaped thus breaking signatures (ignoring RfC 4880 recommendation)
https://bugs.kde.org/show_bug.cgi?id=303305 --- Comment #3 from Hauke Laging ha...@laging.de --- (In reply to comment #1) could you paste screenshot about it ? Sure. Now I have noticed that KMail shows the escape char . I am not familiar enough with the RfCs for emails without crypto but I guess that the MUA should strip off that one when displaying the message. For the crypto component it would be useful to check in case of both a bad signature and a From whether the signature validates against a modified body (without the ). -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295043] New: openpgp signature of expired key is shown as invalid
https://bugs.kde.org/show_bug.cgi?id=295043 Summary: openpgp signature of expired key is shown as invalid Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: crypto AssignedTo: kdepim-bugs@kde.org ReportedBy: ha...@laging.de Version: unspecified (using KDE 4.6.0) OS:Linux After the expiration of the signing key the signature is shown as invalid. Not even the details give any hint to the real problem. Even worse: It is as far as I can see exactly the same behaviour like with a bad signature. GnuPG knows these statuses for signatures (see /usr/share/doc/packages/gpg2/DETAILS): GOODSIG EXPSIG EXPKEYSIG REVKEYSIG BADSIG ERRSIG VALIDSIG It seems to me that kmail tells apart only GOODSIG on the one hand and the rest on the other. And for the first case the different TRUST_* levels. I think this can be considered a bug. Reproducible: Always Steps to Reproduce: Click on the mail. Expected Results: EXPSIG and EXPKEYSIG should be treated like the combination GOODSIG/TRUST_UNDEFINED i.e. show the mail border in yellow and tell the user about the problem in the details section. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 273428] New: bind identities to recipients (for mailinglists and privacy)
https://bugs.kde.org/show_bug.cgi?id=273428 Summary: bind identities to recipients (for mailinglists and privacy) Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: composer AssignedTo: kdepim-bugs@kde.org ReportedBy: ha...@laging.de Version: unspecified (using KDE 4.6.0) OS:Linux It would make sense to be able to configure a certain identity for recipients (and a default identity for each own email address). There are three problems which would be solved by that: 1) Mailinglists usually hide the recipient's address so it is not possible to select the right identity. I often have to check which of my addresses to use as from address before I write to a mailinglist. The correct address should be chosen automatically. 2) When using forwarding addresses (which are not used as from) automatic selection fails in the same way. 3) I use several identities for the same email address. They differ in the signature. When sending mail to people from an organization I am a member of then I put non-public links in my signature. It could be bad if accidentally used the wrong identity for sending (mainly: replying to) mail. KMail should use the default identity unless the recipient is permanently or the composer window is manually configured to use a certain identity. It would make sense to have both a global default identity (which is used when you write a new mail) and a default identity for each email address (which is used when replying). Reproducible: Always -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 94114] posibility to encrypt received unencrypted emails
http://bugs.kde.org/show_bug.cgi?id=94114 Hauke Laging hauke laging de changed: What|Removed |Added CC||ha...@laging.de --- Comment #4 from Hauke Laging hauke laging de 2009-01-08 01:08:40 --- (In reply to comment #1) Even though I'm not one of the developers, in my opinion this would be a bad idea. With this logic _every_ program should have to include its own encryption backend because the data it handles is possibly sensitive. That's a strange argument as far as IMAP storage is concerned. Please mind that more and more people switch from POP3 to IMAP. There is no other option for protecting data on IMAP. It would be neither a program-specific backend (because you can use GPG for any kind of data) nor be new as kmail already has the capability to decrypt and encrypt emails. The only change would be to encrypt a received mail instead of a sent one. General encryption of files should be handled as such: encrypted files or filesystems. Correct but irrelevant as this is not an option for those who use an IMAP service provider (does not make sense to propose everyone might set up his own IMAP server just in order to get around this simple and elegant solution by forcing volume encryption to become an option). -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
