![]() ![]() So looking at this, it seems more doable. For the protocol/boundary: package/mime.jsm Įnigma mail also uses OpenPGP as their default crypto api: package/cryptoAPI.jsm.I think Enigma mail can be of great help here and a few of their routines can be copied, e.g.: For S/MIME, we have the email content and then the signature as an smime.p7s file attachment. The Content-Type determines the protocol and boundary which separates the different parts. This is an OpenPGP/MIME signed message (RFC 48)Ĭontent-Type: multipart/mixed boundary="uiIUBLASCNUasibfu7asulbfyasv23bkasus"Ĭontent-Type: application/pgp-signature name="signature.asc"Ĭontent-Description: OpenPGP digital signatureĬontent-Disposition: attachment filename="signature.asc" PGP (and autocrypt): Autocrypt: prefer-encrypt=mutual Ĭontent-Type: multipart/signed micalg=pgp-sha1 īoundary="tasydia7BASYD6KDBUASIGfkaug7askjaba".=_Part_12371878_129837423.1610754987387-Ĭontent-Type: application/pkcs7-signature name=smime.p7s smime-type=signed-dataĬontent-Disposition: attachment filename="smime.p7s"Ĭontent-Description: S/MIME Cryptographic Signature the right string goes into the right openPGP function. So we just need to make sure that the email is parsed correctly, s.t. ![]() I’m not an expert but I’d assume once the mail is parsed these operations are applied to the corresponding parts.įor all the crypto operations we should use an external library like OpenPGPjs. So I assume the difficult part is to implement the encryption/decryption and signing/verification. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |