From: Richard Levitte Date: Thu, 19 Feb 2026 12:30:13 +0000 (+0100) Subject: doc: enumerate and describe known reserved property names X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=72830bbec3bea4b4306c1b8019230f086bcaa5e9;p=thirdparty%2Fopenssl.git doc: enumerate and describe known reserved property names Reviewed-by: Dmitry Belyavskiy Reviewed-by: Paul Dale MergeDate: Wed Feb 25 11:00:15 2026 (Merged from https://github.com/openssl/openssl/pull/30083) --- diff --git a/doc/man7/property.pod b/doc/man7/property.pod index eb0f6b176c..594a72956e 100644 --- a/doc/man7/property.pod +++ b/doc/man7/property.pod @@ -142,6 +142,38 @@ Note that the local property query could not use "fips=no" because that would disallow any implementations with "fips=yes" rather than not caring about the setting. +=head1 PREDEFINED NAMES + +=for comment This list should correspond to the array 'predefined_names' in crypto/property/property_parse.c + +Currently known predefined names are: + +=over 4 + +=item C + +The conventional property value is the provider's name. This may be different from the name returned by L. + +It is a convention among OpenSSL provider implementations to define a property with this name. It is not mandatory to do this. + +=item C + +The conventional property value is the provider's version. + +OpenSSL provider implementations do not define a property with this name. + +=item C + +The conventional property value is boolean (C<"yes"> or C<"no">), indication whether the implementation conforms to FIPS standards or not. + +It is a convention among OpenSSL provider implementations to define a property with this name where applicable. It is not mandatory to do this, but is strongly recommended. + +=item C, C, C + +Properties with these names are used by encoders (see L) and decoders (see L). + +=back + =head1 SYNTAX The lexical syntax in EBNF is given by: