[Top] [All Lists]

Re: [openpgp] "OpenPGP Simple"

2015-03-16 17:03:50
On Monday, March 16, 2015, David Shaw <dshaw(_at_)jabberwocky(_dot_)com> wrote:

On Mar 16, 2015, at 5:15 PM, David Leon Gil <coruus(_at_)gmail(_dot_)com
<javascript:;>> wrote:

Re Jon's comment above: The five-octet, new-format thing is what the
End-to-End extension does.

On Monday, March 16, 2015, Werner Koch <wk(_at_)gnupg(_dot_)org 
On Mon, 16 Mar 2015 19:12, singpolyma(_at_)singpolyma(_dot_)net 

Yes.  Last time I checked, gnupg < 2 (which is still the default on
most of my systems) only generates old-style headers, whereas my

That depends on how you invoke gpg and whether the new packer headers
are required.  That is required for PGP-2 compatibility.

Is there an option to completely disable this?

Not in the current code, but you can of course patch it.

Relatedly, is there any option to not use new-format partial lengths?

A partial length is needed to handle content as a stream - say some
program that generates gigabytes of data (like a backup).  Something large
enough that you really don't want to have to buffer the whole thing before
encrypting it.

I agree on that. But I think this really requires a different mode of
operation / standard. See, e.g., I'm not
sure that an OpenPGP WG is the right place to do this.

(Which is why I said that the scope should be limited to email-length


But, e.g., GnuPG (always?) emits partial lengths, even for data it already
knows the length of (and is << even 2^20 bytes).
openpgp mailing list