On 14.02.2019 01:13, Noodles via enigmail-users wrote: [...] A PGP/MIME message needs to verify *everything* within the first section of the multipart/signed message. I marked the part with #.
MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature" micalg=pgp-sha256; boundary="---------------------i6v6xkxfcyrp6486l406uof887n42li5"; charset=UTF-8 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) -----------------------i6v6xkxfcyrp6486l406uof887n42li5 # Content-Type: multipart/mixed; # boundary=---------------------yfgbj0fktxh9pfgqxbdq1ehdbm62dfys # #-----------------------yfgbj0fktxh9pfgqxbdq1ehdbm62dfys #Content-Type: multipart/alternative; # boundary=---------------------fujsoqrfmpwp177zji13yuzv1gwrz2sq # ... # # -----------------------yfgbj0fktxh9pfgqxbdq1ehdbm62dfys-- # -----------------------i6v6xkxfcyrp6486l406uof887n42li5 Content-Type: application/pgp-signature; name="signature.asc" ... -----------------------i6v6xkxfcyrp6486l406uof887n42li5 [...] > Please let me know exactly what all subsections of the raw email does > the protonmail webclient uses to formulate the standard PGP signature. Why do you ask at the Enigmail mailing list how Protonmail creates a signature? -Patrick _______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
