Bug#898634: kmail: efail attack against S/MIME
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Wed, 2018-05-16 at 12:33 +0200, Sandro Knauß wrote:
> > Thanks, that's good to know.
>
> Should I prepare a update with those patches for stable?
Yes I think it'd be worth it.
>
> > > For a more detailed look for KMail and EFail see the dot.kde article:
> > >
> > > https://dot.kde.org/2018/05/15/efail-and-kmail
> >
> > That article indicates KMail uses GnuPG for S/MIME, which I find a bit
> > weird.
> Okay it is simplyfied a lot - but in the end... GPGME itself using gpg-agent
> etc. to request the work, so in the end it is the normal GnuPG pipeline, that
> is doing the work, without parsing comandline output :) But for more detailed
> look I wrote a blog post about the whole crypto stack some while ago:
> https://exote.ch/blogs/sandro/kontact-and-gnupg-under-windows/
There's a misunderstanding. My point isn't about PGP/MIME (which is indeed
handled by gnupg, even if through gpgme), but about S/MIME, which I really
don't think it handled by anything related to gnupg.
Regards,
- --
Yves-Alexis
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlr8DW8ACgkQ3rYcyPpX
RFsDIAf8DJe2LkURVnSyWskcAW9zer3zZHkHsWke9FhFbRIzulbMMco4s6bNSGnC
n2jh2VdA/6vdNKPq5LqczAmiZVto8OOeX6unWhoJ/egvTiVgCQLdnnT7NHOh5VXM
2GDssF2DQmvI/rE5WYzNr51DunqAeodzhZeZfGOfjBqugKTgj3bhAiQglvti/Q+L
Y40nQf0yD+00DkDlTcuJGXJSN52HbsepraoS80z3t22SUSwXdEn+dhTMDw+Lh0qh
Kq7AZIrHUT6EvhsIqV75OsJb56+xjOHaGnuSa01SjRooF+ACnG2WPh4W88C/77gq
zlQqqwW8dWws2SdcO3LSKn055PSKow==
=JsqI
-----END PGP SIGNATURE-----
Reply to: