From a8e2a9f569c60dbbc180672b0fce16ab7dd6ca72 Mon Sep 17 00:00:00 2001 From: "Dr. David von Oheimb" Date: Fri, 4 Sep 2020 18:31:46 +0200 Subject: [PATCH] X509_NAME_add_entry_by_txt.pod: Improve documentation w.r.t. multi-valued RDNs (containing sets of AVAs) Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/12769) --- doc/man3/X509_NAME_add_entry_by_txt.pod | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/man3/X509_NAME_add_entry_by_txt.pod b/doc/man3/X509_NAME_add_entry_by_txt.pod index ce8bf3ef29..8b17a016de 100644 --- a/doc/man3/X509_NAME_add_entry_by_txt.pod +++ b/doc/man3/X509_NAME_add_entry_by_txt.pod @@ -66,13 +66,13 @@ RelativeDistinguishedName (RDN). B actually determines the index where the new entry is inserted: if it is -1 it is appended. -B determines how the new type is added. If it is zero a -new RDN is created. +B determines how the new type is added. +If it is zero a new RDN is created. -If B is -1 or 1 it is added to the previous or next RDN -structure respectively. This will then be a multivalued RDN: -since multivalues RDNs are very seldom used B is almost -always set to zero. +If B is -1 or 1 it is added as a new set member +to the previous or next RDN structure, respectively. +This will then become part of a multi-valued RDN (containing a set of AVAs). +Since multi-valued RDNs are very rarely used B typically will be zero. =head1 RETURN VALUES -- 2.34.1