[Info-vax] OpenSSL CSWS-2.2-1

[Craig A. Berry]

On 4/29/19 11:06 AM, Craig A. Berry wrote:
> On Monday, April 29, 2019 at 10:24:15 AM UTC-5, doug... at aol.com wrote:
>   
>> OpenSSL 1.1.1(b) kits have been developed and will be released soon
>> (TLS V1.3 support). The product name will likely be SSL111 and maintain
>> the same install structure as SSL1 (separate directory trees for co-existence).
> 
> SSL11 would make more sense than SSL111 in that it preserves those
> parts (and only those parts) of the version number indicating a
> binary compatible release.  There may never be a 1.1.2, but if there
> is, it will be binary compatible with 1.1.1, so no need for a new
> product name.

Oh well, I tried.  They just released it and the product name is indeed
SSL111.  So eventually we'll be going cross-eyed over things like
version V1.1-2C of a product named SSL111.

> While it will probably throw a wrench into human-readable version
> comparisons for those versions that already exist, v3.x.x might be a
> good time to deal with the fact that in a few years there will likely
> be an OpenSSL 10.x.x.  A product name like SSL0300 for a release
> based on OpenSSL 3.0.x would have an obvious relationship to a
> product called SSL1013 and based on OpenSSL 10.13.x.

I'm revising this advice slightly (not that it's any more likely to be
followed than my advice above) based on the fact that beginning with
OpenSSL 3.0.0, all versions sharing a major version number will be
binary compatible.  So a product name of SSL03 would be sufficient for
everything in the 3.x.x series.