<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 21/05/2018 09:54, Damien Goutte-Gattat via Gnupg-users wrote:<br>
<blockquote
cite="mid:c2670243-45b8-d740-1edd-18a884f221dc@incenp.org"
type="cite">
<pre wrap="">On 05/21/2018 04:07 AM, Mark Rousell wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I think you mean that support for 2.0.y has been dropped, surely?
</pre>
</blockquote>
<pre wrap="">
No, I do mean that support for all PGP 2-related stuff has been dropped
from the current stable branch. Modern GnuPG (≥ 2.1) can neither read
nor write anything that has been generated by PGP 2.x. Compatibility
starts with PGP 5, which dates back to 1997.
</pre>
</blockquote>
<br>
Ah, gotcha. I was being careless over terminology.<br>
<br>
<br>
<blockquote
cite="mid:c2670243-45b8-d740-1edd-18a884f221dc@incenp.org"
type="cite">
<blockquote type="cite">
<pre wrap="">When I wrote "2.x.y" above I meant that users should be able
to continue decrypting legacy-encrypted data (albeit with a change of
commands/options compared to the present) with whatever the
currently-supported version of 2.something is at any point in the
future.
</pre>
</blockquote>
<pre wrap="">
Well, that's already not the case. If you have pre-1997 data, you need
to use GnuPG 1.4, which again *is* still supported precisely for this
use case. (You could also, in theory, use GnuPG 2.0.x, but *that* branch
is explicitly no longer supported.)
</pre>
</blockquote>
<br>
Thanks. This satisfies my preferences, that legacy-encrypted data
can be decrypted with maintained code.<br>
<br>
<pre class="moz-signature" cols="72">--
Mark Rousell</pre>
</body>
</html>