Daniel Kahn Gillmor writes:
> Inline PGP encrypted messages are clearly worse than PGP/MIME
> structured encrypted messages. There are no standards for how they
> are formed, and they don't offer any structured metadata about how to
> interpret the bytestream produced by
On Mon 2018-04-30 08:42:24 -0300, David Bremner wrote:
> David Bremner writes:
>
>> Daniel Kahn Gillmor writes:
>>
>>> We make use here of GMime's optimization function for detecting the
>>> presence of inline PGP encrypted content, which is only found
David Bremner writes:
> Daniel Kahn Gillmor writes:
>
>> We make use here of GMime's optimization function for detecting the
>> presence of inline PGP encrypted content, which is only found in GMime
>> 3.0 or later.
>
> We nominally support gmime-2.6
Daniel Kahn Gillmor writes:
> We make use here of GMime's optimization function for detecting the
> presence of inline PGP encrypted content, which is only found in GMime
> 3.0 or later.
We nominally support gmime-2.6 still. Maybe we shouldn't anymore, but
that's a
Inline PGP encrypted messages are clearly worse than PGP/MIME
structured encrypted messages. There are no standards for how they
are formed, and they don't offer any structured metadata about how to
interpret the bytestream produced by decrypting them.
However, some other MUAs and end-user