On Fri, Apr 19, 2024 at 01:59:57AM +0200, Alejandro Colomar wrote:
BTW, now that I remember, while developing these things for neomutt(1), I found that mutt(1) has a bug (?) by which it does actually protect some header fields precisely in the way that I implemented them in neomutt(1), with the difference that mutt(1) does it on accident.
As Derek mentioned, mutt is in maintenance mode. I don't have much, if any, time available to address issues except for genuine crashes or vulnerabilities.
However, I'd like to point out that mutt added basic support for Protected Headers in the 2.0 release, following the Autocrypt project spec at the time <https://github.com/autocrypt/protected-headers>. Since then, undoubtedly, they've advanced the proposed spec, but I haven't followed it.
However, saying that mutt adds those headers by accident or as a bug seems a bit uninformed.
-- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
