From: Eluminae <Eluminae@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Encrypt + Sign
Date: Tue, 02 Feb 2021 12:56:11 +0100 [thread overview]
Message-ID: <20210202115611.CXDIdH6ZJI8UPCPxsnwEY5tx9PGngUxLWJLB0RGMakY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-202@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1737 bytes --]
New comment by Eluminae on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/202#issuecomment-771584792
Comment:
I think the encrypted part contain in itself multiple subparts. mblaze in it current state can't know about the signature encrypted subpart.
Here the mpgp filter stdout
```
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="===============2511636010367206221=="
MIME-Version: 1.0
--===============2511636010367206221==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
This is a test email sent from sourcehut to confirm that PGP is working as you
expect. This email is signed with this key:
447B 69E4 B34B E90B C829 A0E9 6597 04D1 A38A 93AE
and is encrypted with this key:
CAB1 2F60 BD13 A21D AB60 C510 5BAC 9232 8B7C 5D65
You may control your PGP settings here:
https://meta.sr.ht/privacy
--
Drew DeVault
sourcehut
--===============2511636010367206221==
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
-----BEGIN PGP SIGNATURE-----
wsBcBAABCgAGBQJgGSvgAAoJEGWXBNGjipOuccMH/18vOX99CyQP/mU8fOe/3YRc
nKCmq0iVdF5WuDNA2grB5Xjat3zEOqzWirUJ2hNcDzJ+rreL5sIltVuK6JnA9hBU
/5VB7xNmJglB04cwkuDaIfbvwVkhKiivTHbY8Y4PbW9k3vH4zYUY8cDvQc8qPCZc
UTHkdXapGz5eTuorFusJB1CaxCgWBrl8xUahJVNyNmMjnqTrpbib8RqWiNAdOjlz
KiH3i/SbIDYscLdFXXSQv+m82fuOD92a60Bac4E//B4XQg9q9YyBGa5fEkS8CXUZ
KULEGLehg/hOxd4Uq7He9xrWoUVS1KtGwTSS7MfSAvYHCPerS+in/UWmlSAvTpQ=
=D3Mk
-----END PGP SIGNATURE-----
--===============2511636010367206221==--
```
The mshow and mless display it as an ordinary subpart but it is a little trickier
next prev parent reply other threads:[~2021-02-02 11:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 10:57 [ISSUE] " Eluminae
2021-02-02 11:05 ` leahneukirchen
2021-02-02 11:34 ` Eluminae
2021-02-02 11:37 ` Eluminae
2021-02-02 11:40 ` Eluminae
2021-02-02 11:41 ` Eluminae
2021-02-02 11:44 ` leahneukirchen
2021-02-02 11:46 ` leahneukirchen
2021-02-02 11:50 ` Eluminae
2021-02-02 11:51 ` Eluminae
2021-02-02 11:56 ` Eluminae [this message]
2021-02-02 11:57 ` leahneukirchen
2021-02-02 11:59 ` leahneukirchen
2021-02-02 12:00 ` leahneukirchen
2021-02-02 12:06 ` Eluminae
2021-02-02 12:07 ` Eluminae
2021-02-02 12:11 ` Eluminae
2021-02-02 12:59 ` Eluminae
2021-02-02 13:10 ` Eluminae
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210202115611.CXDIdH6ZJI8UPCPxsnwEY5tx9PGngUxLWJLB0RGMakY@z \
--to=eluminae@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).