summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/X509_STORE_set1_param.3
diff options
context:
space:
mode:
authorschwarze <>2018-04-01 00:36:28 +0000
committerschwarze <>2018-04-01 00:36:28 +0000
commit19ca27005331c7a91aa7c035f28984463af71c84 (patch)
treed68bda8b9354fb1fa31660be4c25fedb4487eef3 /src/lib/libcrypto/man/X509_STORE_set1_param.3
parent305fd53b371c0bfd8018f8401c64f25853e8b475 (diff)
downloadopenbsd-19ca27005331c7a91aa7c035f28984463af71c84.tar.gz
openbsd-19ca27005331c7a91aa7c035f28984463af71c84.tar.bz2
openbsd-19ca27005331c7a91aa7c035f28984463af71c84.zip
When you replace an element in a sorted array with something
arbitrarily different, the array is in general no longer sorted. This commit copies a small hidden bugfix from the OpenSSL commit https://github.com/openssl/openssl/commit/fbb7b33b the rest of which is merely cosmetics. I discovered the bug independently while documenting sk_find(3). Keep the library's idea of when an empty stack or a one-element stack is sorted and when it is not bug-compatible with OpenSSL, even though in fact, empty and one-element stacks are of course always sorted. OK beck@
Diffstat (limited to 'src/lib/libcrypto/man/X509_STORE_set1_param.3')
0 files changed, 0 insertions, 0 deletions