summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/doc/RSA_set_method.pod
diff options
context:
space:
mode:
authormmcc <>2016-03-12 21:31:22 +0000
committermmcc <>2016-03-12 21:31:22 +0000
commitd7e23979f786be3c146be16ec4363c6da83c906e (patch)
tree41d48a54c09f49f4e37617cd4f79d217bf4250a8 /src/lib/libcrypto/doc/RSA_set_method.pod
parent7dcc5e245914ca63e2d707bd58bb281cadf8e648 (diff)
downloadopenbsd-d7e23979f786be3c146be16ec4363c6da83c906e.tar.gz
openbsd-d7e23979f786be3c146be16ec4363c6da83c906e.tar.bz2
openbsd-d7e23979f786be3c146be16ec4363c6da83c906e.zip
Remove sentences in RETURN VALUES sections saying that functions with
void return types 'return no value'. This is obvious and therefore unneccessary to mention. We spare rewind(3)'s sentence because espie@ pointed out that it's a warning - the function masks a potential error. This commit also adds a sentence to X509_free clarifying that it's NULL-safe. This bit was discussed with doug@. ok martijn@, sentiment supported by schwarze@
Diffstat (limited to 'src/lib/libcrypto/doc/RSA_set_method.pod')
-rw-r--r--src/lib/libcrypto/doc/RSA_set_method.pod2
1 files changed, 0 insertions, 2 deletions
diff --git a/src/lib/libcrypto/doc/RSA_set_method.pod b/src/lib/libcrypto/doc/RSA_set_method.pod
index 7f687c8718..3f50a89e5c 100644
--- a/src/lib/libcrypto/doc/RSA_set_method.pod
+++ b/src/lib/libcrypto/doc/RSA_set_method.pod
@@ -142,8 +142,6 @@ the default method is used.
142RSA_PKCS1_SSLeay(), RSA_PKCS1_null_method(), RSA_get_default_method() 142RSA_PKCS1_SSLeay(), RSA_PKCS1_null_method(), RSA_get_default_method()
143and RSA_get_method() return pointers to the respective RSA_METHODs. 143and RSA_get_method() return pointers to the respective RSA_METHODs.
144 144
145RSA_set_default_method() returns no value.
146
147RSA_set_method() returns a pointer to the old RSA_METHOD implementation 145RSA_set_method() returns a pointer to the old RSA_METHOD implementation
148that was replaced. However, this return value should probably be ignored 146that was replaced. However, this return value should probably be ignored
149because if it was supplied by an ENGINE, the pointer could be invalidated 147because if it was supplied by an ENGINE, the pointer could be invalidated