From: xelxebar <xelxebar@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Handling of encrypted PGP/MIME multipart messages
Date: Sun, 12 Feb 2023 14:13:30 +0100 [thread overview]
Message-ID: <20230212131330.saUr4VFI1e0GnXlYsx5xqKPALBl9v83CYd7jRXte5_I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-175@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 316 bytes --]
New comment by xelxebar on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/175#issuecomment-1427030335
Comment:
Late to the party here, but I'm just doing something way dumber here: `mgpgshow(){ mraw "$1" | gpg --decrypt | mshow -;}`.
That said. It would be nice to also verify the signature.
prev parent reply other threads:[~2023-02-12 13:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 19:53 [ISSUE] " nmeum
2020-05-16 20:03 ` leahneukirchen
2020-05-16 20:05 ` leahneukirchen
2020-05-17 8:34 ` [ISSUE] [CLOSED] " nmeum
2020-05-23 13:35 ` leahneukirchen
2020-05-23 15:10 ` nmeum
2023-02-12 13:13 ` xelxebar [this message]
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=20230212131330.saUr4VFI1e0GnXlYsx5xqKPALBl9v83CYd7jRXte5_I@z \
--to=xelxebar@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).