How to convert (ancient) key in "version 2" to more modern "version 4" format?

Bjoern Kahl mls at
Sun May 29 00:04:13 CEST 2016

 Dear Ludwig,

Am 28.05.16 um 22:24 schrieb Ludwig Hügelschäfer:
> On 28.05.16 20:30, Bjoern Kahl wrote:
>> Which leaves me with the other option, teach mailvelop /
>> openpgp.js to read v2 keys.
>> Looking at the RFC-4880, it seems V3 and V2 keys share the same 
>> structure (section 5.5.2, page 41).  Openpgp.js does handle V3
>> keys, but not V2.  Which makes me wonder if it is enough to let V2
>> keys run through the same code path as the supported V3 keys, or if
>> I am missing something important here.
> Björn, why would you want to put energy in support of such ancient
> keys? V3 keys aren't supported any more by GnuPG 2.1, and nobody
> mentioned V2 keys here for years. Usually, those keys are at best 1024
> bits long which suggests that they are replaced by a adequate V4 key
> with recommended key length right now.

 Very simple:

 Because I have *tons* of mails (and other archived data files) that
 have been signed and / or encrypted with such keys and I (I have to
 use such a strong word here) *insist* on being able to continue to
 read these mails and files whenever the need arises.

> They are obsolete in every aspect.

 They may not be a wise choice for creating new data (mails, files) for
 their limited key length and other shortcomings mentioned in 4880 and
 elsewhere.  But they are perfectly fine and necessary to access
 historic data.



|     Bjoern Kahl   +++   Siegburg   +++    Germany     |
|     "mls at -my-domain-"   +++     |
| Languages: German, English, Ancient Latin (a bit :-)) |

More information about the Gnupg-users mailing list