From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Adam Sjøgren" <asjo@koldfront.dk>
Cc: info-gnus-english@gnu.org
Subject: Re: Subject of PGP-encrypted emails
Date: Wed, 04 Aug 2021 09:11:03 +0200 [thread overview]
Message-ID: <875ywlhego.fsf@gnus.org> (raw)
In-Reply-To: <877dh2jtdo.fsf@tullinup.koldfront.dk> ("Adam =?utf-8?Q?Sj?= =?utf-8?Q?=C3=B8gren=22's?= message of "Tue, 03 Aug 2021 20:05:55 +0200")
Adam Sjøgren <asjo@koldfront.dk> writes:
> I noticed that instead of including an unencrypted Subject:-header, it
> is replaced by "Subject: ..." and then 'filled in' when the message is
> decrypted.
Hm... I guess it would be possible to update the Summary buffer, too,
but it'd be pretty awkward -- do we want to redo the threading, for
instance?
> I wonder if anyone has looked into adapting Gnus to do something similar?
>
> Or maybe just do the same extraction and 'filling in' of the Subject:
> when reading an encrypted email sent from Thunderbird.
>
> It looks like what Thunderbird does it that it generates an
> encrypted.asc which decrypts to a MIME message, which has a part that
> includes the Subject:-header:
>
> Content-Type: multipart/mixed; boundary="80MRq3onMnRYcWyMqpzN3xR7VKumL3WsW";
> protected-headers="v1"
> Subject: Dette er emnelinien
> From: Test Testersen <test@koldfront.dk>
> To: =?UTF-8?Q?Adam_Sj=c3=b8gren?= <asjo@koldfront.dk>
> Message-ID: <f66d7c92-9cfb-28ec-3f50-5e7c1132c832@koldfront.dk>
>
> So the display-part is perhaps easier than the sending part.
We could update the headers in the Article buffer easily enough, but on
the other hand -- if the user wants to respond to this in clear text,
hitting `C-d' first is easy enough, and ... do we want to encourage
responding to encrypted stuff in clear text? (I mean, if we just
rewrite the Article buffer Subject/From/etc headers, then hitting `r'
will use those, and then we might reveal... stuff...)
> I also noticed that Thunderbird included an Autocrypt:-header, which
> seems to include the public key of the sender - I haven't looked into
> it, but it might be worth adding support for that in Gnus as well? Or
> maybe it's a waste of bandwidth...
What does the Autocrypt header do?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-08-04 7:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 18:05 Adam Sjøgren
2021-08-04 7:11 ` Lars Ingebrigtsen [this message]
2021-09-02 7:47 ` Alberto Luaces
2021-09-02 8:38 ` Colin Baxter
2021-09-02 8:55 ` Alberto Luaces
2021-09-02 9:11 ` Colin Baxter
2021-09-02 9:18 ` Alberto Luaces
2021-09-02 9:50 ` Colin Baxter
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=875ywlhego.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=asjo@koldfront.dk \
--cc=info-gnus-english@gnu.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).