News for hackers. Stuff that matters.
Re:Rnp: An OpenPGP Library in C++ by tptacek on Saturday July 13, 2019 @01:14PM (#20429047)
S/MIME is even worse than PGP.
Re:Rnp: An OpenPGP Library in C++ by Avamander on Saturday July 13, 2019 @01:23PM (#20429082)
S/MIME has better e-mail client support and has massive deployment (use, not that much) in Estonia. I think it already beats PGP in two major aspects with that.
Re:Rnp: An OpenPGP Library in C++ by tptacek on Saturday July 13, 2019 @02:20PM (#20429395)
S/MIME manages the feat of being even less secure than PGP-encrypted email, which was, again, a low bar to trip over.
Re:Rnp: An OpenPGP Library in C++ by Avamander on Saturday July 13, 2019 @02:53PM (#20429549)
Please elaborate.
Re:Rnp: An OpenPGP Library in C++ by wolf550e on Sunday July 14, 2019 @10:01AM (#20433415)
I think efail showed S/MIME was even more susceptible.
Re:Rnp: An OpenPGP Library in C++ by Avamander on Sunday July 14, 2019 @10:33AM (#20433605)
That vulnerability has been largely mitigated, hasn't it? I'm really curious how GPG is more secure than S/MIME right now.
Re:Rnp: An OpenPGP Library in C++ by wolf550e on Sunday July 14, 2019 @01:45PM (#20434699)
"8.2 Countering malleability gadget attacks" in the efail paper says: "The S/MIME standard does not provide any effective security measures countering our attacks" and "Although CMS defines an AuthenticatedData type [29], S/MIME’s current specification does not."

If the S/MIME spec does not enforce (and it seems it doesn't even allow, not just does't enforce) Authenticated Encryption, then it violates "the cryptographic doom principle" and should not be used for anything except CTFs and cryptopals exercises.

Re:Rnp: An OpenPGP Library in C++ by Avamander on Sunday July 14, 2019 @11:46PM (#20437977)
The effective measure against their attack is signing and encrypting your e-mail sent with S/MIME? If it's just encrypted then yes, there's malleability issues but if it's signed I don't see it happening.