From: Eluminae <Eluminae@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Encrypt + Sign
Date: Tue, 02 Feb 2021 11:57:22 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-202@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
New issue by Eluminae on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/202
Description:
I just configured filters with some contrib scripts from this repo and I received this mail
```
--- 1: multipart/encrypted size=2246 filter="mgpg" ---
--- --- 2: multipart/signed size=1138 ---
--- --- --- 3: text/plain size=356 ---
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
--- --- --- 4: application/pgp-signature size=455 name="signature.asc" render="mverify; exit 0" ---
No signature found.
```
It seems this signature could not be verified.
After some check, it seems I can't send an encrypted + signed email too
In recap:
* Is it possible to encrypt then sign ? Or to encrypt+sign in one action (maybe easier) ?
* Does mverify and/or mpgp could handle signed crypted messages ?
next reply other threads:[~2021-02-02 10:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 10:57 Eluminae [this message]
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
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=gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-202@inbox.vuxu.org \
--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).