Bug#766349: Kmail: Some times sign with S/MIME failed
On November 1, 2014 12:52:01 AM CDT, "Jörg Frings-Fürst" wrote: >Hi, > > >Am Samstag, 1. November 2014, 00:22:43 schrieb Scott Kitterman: >> Is there a pattern about when it fails and when it doesn't? > >No, only that I can sign 3 or 4 mail and then all other failed without >any >errormessage. > >For me I think is a memory hole... > > >> >> When you filed this bug, you filed it at severity critical. In >Debian, >> critical is defined as: >> >> critical >> makes unrelated software on the system (or the whole system) >break, or >> causes serious data loss, or introduces a security hole on systems >where you >> install the package. >> > >I think that a not or wrong encrypted or signed mail is already a >security >issue. Failing to sign and failing to encrypt have different impacts (and thus severity). Is it also failing to encrypt? The bug only mentions signing. Scott K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#766349: Kmail: Some times sign with S/MIME failed
severity 766349 grave thanks Hello, kmail signed or encrypted emails without any user notice incorrect. So is kmail unusable. Therefore I set the severity to grave. CU Jörg -- pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E CAcert Key S/N: 0E:D4:56 Jörg Frings-Fürst D-54526 Niederkail Threema-ID: SYR8SJXB IRC: j_...@freenode.net, j_...@oftc.net signature.asc Description: This is a digitally signed message part.
Bug#766349: Kmail: Some times sign with S/MIME failed
Hi, Am Samstag, 1. November 2014, 00:22:43 schrieb Scott Kitterman: > Is there a pattern about when it fails and when it doesn't? No, only that I can sign 3 or 4 mail and then all other failed without any errormessage. For me I think is a memory hole... > > When you filed this bug, you filed it at severity critical. In Debian, > critical is defined as: > > critical > makes unrelated software on the system (or the whole system) break, or > causes serious data loss, or introduces a security hole on systems where you > install the package. > I think that a not or wrong encrypted or signed mail is already a security issue. > This does not seem to fit that criteria, so I'm going to adjust the > severity. > > Scott K CU Jörg -- pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E CAcert Key S/N: 0E:D4:56 Jörg Frings-Fürst D-54526 Niederkail Threema-ID: SYR8SJXB IRC: j_...@freenode.net, j_...@oftc.net signature.asc Description: This is a digitally signed message part.
Bug#766349: Kmail: Some times sign with S/MIME failed
Is there a pattern about when it fails and when it doesn't? When you filed this bug, you filed it at severity critical. In Debian, critical is defined as: critical makes unrelated software on the system (or the whole system) break, or causes serious data loss, or introduces a security hole on systems where you install the package. This does not seem to fit that criteria, so I'm going to adjust the severity. Scott K signature.asc Description: This is a digitally signed message part.
Bug#766349: Kmail: Some times sign with S/MIME failed
found 766349 + kdepim/4:4.14.2-1 thanks Hi, also found in kdepim/4:4.14.2-1 CU Jörg -- pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E CAcert Key S/N: 0E:D4:56 Jörg Frings-Fürst D-54526 Niederkail Threema-ID: SYR8SJXB IRC: j_...@freenode.net, j_...@oftc.net signature.asc Description: This is a digitally signed message part.
