openbsd/src/lib/libssl/man/SSL_get_shared_ciphers.3, branch OPENBSD_7_9

.Lb libssl libcrypto ; OK tb@

2025-06-08T22:52:00+00:00

Update SSL_get_shared_ciphers() documentation for ssl_lib.c r1.240

2021-01-09T10:50:02+00:00

From schwarze, who explains: * Even though i wrote the original version of our documentation for this function, i now think the design of this function is so atrocious that it is better to call out the main limitations up front (server side only and silent truncation) rather than first giving the impression that it achieves something it actually doesn't and then later try to row back in a piece-meal manner. * Using a .Bl list for failure conditions in the RETURN VALUES section is no doubt unusual, but the conditions are so numerous and some of them are so surprising that i think it makes sense in this case. If a function is badly designed and has surprising properties, precision and clarity in the description are even more important than usual, and conciseness is better sacrificed. * Adding .Xr SSL_get_ciphers 3 seems helpful. ok beck inoguchi jsing tb

add missing backlinks to ssl(3)

2019-06-12T09:36:30+00:00

found a complete archive of SSLeay-0.4 to SSLeay-0.8.1b tarballs

2018-03-27T17:35:50+00:00

on the web, so fix up SSLeay HISTORY accordingly

ssl.h HISTORY up to SSLeay 0.8.1b; researched from OpenSSL git

2018-03-21T05:07:04+00:00

Write an SSL_get_shared_ciphers(3) manual from scratch; another one

2016-12-10T14:56:56+00:00

where BUGS is longer than DESCRIPTION. The function is listed in ssl(3) and , so it's clearly public. The code looks slightly mysterious to me, so it would be welcome if somebody more familiar with TLS protocols could check factual accuracy.