Documenting lack of error codes stability

Reviewed-by: Hugo Landau <hlandau@openssl.org>
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/20019)
This commit is contained in:
Dmitry Belyavskiy 2023-01-10 18:54:51 +01:00
parent 60c3d732b7
commit ae61bd34e6
1 changed files with 8 additions and 0 deletions

View File

@ -42,6 +42,14 @@ The library number, reason code, and whether the error
is fatal, respectively.
Starting with OpenSSL 3.0.0, the function code is always set to zero.
=head1 NOTES
Applications should not make control flow decisions based on specific error
codes. Error codes are subject to change at any time (even in patch releases of
OpenSSL). A particular error code can only be considered meaningful for control
flow decisions if it is explicitly documented as such. New failure codes may
still appear at any time.
=head1 SEE ALSO
L<ERR_get_error(3)>