The ECDH callback needs to query the server's certificate to discover
the EC group being used. The callback can then return a temporary key
in the field.
It looks like SSL_get_certificate can be used for the purpose.
SSL_get_certificate is used in apps/s_cb.c, but there's no
documentation for it.
Patch applied.
Many thanks,
Matt
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager m
There's a very useful -timeout option in the ocsp utility which is not
mentioned in the manpage or the help output.
diff --git a/apps/ocsp.c b/apps/ocsp.c
index 902546f..0c6579d 100644
--- a/apps/ocsp.c
+++ b/apps/ocsp.c
@@ -650,6 +650,7 @@ int MAIN(int argc, char **argv)
BIO_prin
To be commit'ed to head shortly, thanks.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Hi,
openssl verify takes the -CRLfile switch to specify a file with CRLs. However
this isn't documented nor does -h show the switch. The attached patch adds some
rudimentary docs in the POD as well as adds it to -h.
Best Regards,
Claes Jakobsson
0001-Added-missing-documentation-and-
The attached patch adds missing documentation for the -no_ign_eof
option.
--
Tomas Mraz
No matter how far down the wrong road you've gone, turn back.
Turkish proverb
diff -up openssl-1.0.0e/doc/apps/s_client.pod.doc-noeof openssl-1.0.0e/doc
I've investigated lacks of documentation in the current OpenSSL
snapshot.
Method of investigation is quite simple
1. Run util/extract-names.pl on the all pod files in the doc/crypto and
doc/ssl and produce sorted list of all function names referenced in the
NAME sections.
2. Take lists of expor
I've investigated lacks of documentation in the current OpenSSL
snapshot.
Method of investigation is quite simple
1. Run util/extract-names.pl on the all pod files in the doc/crypto and
doc/ssl and produce sorted list of all function names referenced in the
NAME sections.
2. Take lists of expor
Richard Levitte - VMS Whacker wrote:
In message <[EMAIL PROTECTED]> on Wed, 29 Jun 2005 06:42:59 +0200, Karsten Ohme
<[EMAIL PROTECTED]> said:
widerstand> will there be some day, when the the OpenSSL source code
widerstand> is documented in a some way? In all source files,
widerstand> explanati
In message <[EMAIL PROTECTED]> on Wed, 29 Jun 2005 06:42:59 +0200, Karsten Ohme
<[EMAIL PROTECTED]> said:
widerstand> will there be some day, when the the OpenSSL source code
widerstand> is documented in a some way? In all source files,
widerstand> explanations to the functions, the parameters an
Hello,
will there be some day, when the the OpenSSL source code is documented
in a some way? In all source files, explanations to the functions, the
parameters and comments in the code what is done are missing. OpenSSL is
the only wide available possibility for a crypto library with this
func
11 matches
Mail list logo