--- Begin Message ---
Thank you, after pulling my hair and almost losing sanity after two long days, 
that worked!

May I know, why does encapsulation has to end with with a <CR><LF> character 
and do all attachments (regardless of the content/nature) after the message 
necessarily need be included to formulate the signature?

Also, where can I find up to date and relevant documentation about PGP/mime 
email structure?

The RFC-3156 page (https://tools.ietf.org/html/rfc3156) confused the hell out 
of me.

> Why do you ask at the Enigmail mailing list how Protonmail creates a
> signature?
Well, sorry for coming off that way, my intention was to know the standard way 
of verifying email messages at client side. I guess I was dumb enough at the 
time to mention protomail.com emails instead of saying, "standard PGP signed 
emails."

Regards,
Random Noodles


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, February 14, 2019 1:35 PM, Patrick Brunschwig 
<[email protected]> wrote:

> 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




--- End Message ---
_______________________________________________
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

Reply via email to