Skip to content

Revert OPENSSL_VERSION_NUMBER status bits back to 0 for all 3.x releases including 3.6 #1621

@esyr

Description

@esyr

The reasons for revert:

  • the issue[1] was originally reported as a result of writing new code[2], not a problem with the existing one;
  • another reference[3] de-facto excludes only 3.0.0/3.0.1 releases which are now irrelevant;
  • the change has broken existing code[4];
  • 3.5.3 is fresh and its usage is low, as opposing to all 3.x releases with 0x0 in the status bits, that were like that for years.

Additional points of consideration:

  • nodejs (and possibly nginx) are to be notified about the revert, in order to avoid causing even more issues;
  • would be nice to document the discrepancy between opensslv.h comment and documentation in the HISTORY section of OpenSSL_version(3ossl).

[1] openssl/openssl#28227
[2] nodejs/node#59436
[3] nginx/nginx@a5ca38f
[4] openssl/openssl#28575

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions