- 28 1月, 2015 1 次提交
-
-
由 Rich Salz 提交于
Remove all "#if 0" blocks from header files. Reviewed-by: NTim Hudson <tjh@openssl.org>
-
- 22 1月, 2015 1 次提交
-
-
由 Matt Caswell 提交于
Reviewed-by: NTim Hudson <tjh@openssl.org>
-
- 04 7月, 2014 1 次提交
-
-
由 Dr. Stephen Henson 提交于
Remove RFC5878 code. It is no longer needed for CT and has numerous bugs
-
- 06 9月, 2013 1 次提交
-
-
由 Scott Deboy 提交于
Add callbacks supporting generation and retrieval of supplemental data entries, facilitating RFC 5878 (TLS auth extensions) Removed prior audit proof logic - audit proof support was implemented using the generic TLS extension API Tests exercising the new supplemental data registration and callback api can be found in ssltest.c. Implemented changes to s_server and s_client to exercise supplemental data callbacks via the -auth argument, as well as additional flags to exercise supplemental data being sent only during renegotiation.
-
- 05 7月, 2012 1 次提交
-
-
由 Richard Levitte 提交于
Add aliases for SSL_CTX_set_not_resumable_session_callback and SSL_set_not_resumable_session_callback on top of that.
-
- 15 12月, 2011 1 次提交
-
-
由 Dr. Stephen Henson 提交于
Submitted by: Peter Sylvester <peter.sylvester@edelweb.fr> Reviewed by: steve Remove unnecessary code for srp and to add some comments to s_client. - the callback to provide a user during client connect is no longer necessary since rfc 5054 a connection attempt with an srp cipher and no user is terminated when the cipher is acceptable - comments to indicate in s_client the (non-)usefulness of th primalaty tests for non known group parameters.
-
- 20 3月, 2011 1 次提交
-
-
由 Richard Levitte 提交于
-
- 23 11月, 2010 1 次提交
-
-
由 Richard Levitte 提交于
build on VMS again.
-
- 26 7月, 2010 1 次提交
-
-
由 Dr. Stephen Henson 提交于
-
- 25 1月, 2010 1 次提交
-
-
由 Richard Levitte 提交于
Submitted by Steven M. Schweda <sms@antinode.info>
-
- 13 11月, 2009 1 次提交
-
-
由 Richard Levitte 提交于
-
- 16 5月, 2009 1 次提交
-
-
由 Richard Levitte 提交于
-
- 26 4月, 2009 1 次提交
-
-
由 Richard Levitte 提交于
-
- 20 4月, 2009 1 次提交
-
-
由 Dr. Stephen Henson 提交于
-
- 16 12月, 2008 1 次提交
-
-
由 Richard Levitte 提交于
-
- 12 4月, 2008 1 次提交
-
-
由 Richard Levitte 提交于
-
- 04 6月, 2006 1 次提交
-
-
由 Richard Levitte 提交于
-
- 29 5月, 2006 1 次提交
-
-
由 Richard Levitte 提交于
-
- 02 3月, 2006 1 次提交
-
-
由 Richard Levitte 提交于
Don't convert a function pointer to a void*, ISO C doesn't like that.
-
- 19 12月, 2005 1 次提交
-
-
由 Andy Polyakov 提交于
from .h files...
-
- 08 9月, 2004 1 次提交
-
-
由 Richard Levitte 提交于
-
- 12 7月, 2004 1 次提交
-
-
由 Richard Levitte 提交于
Lucky me, I had prepared for this :-).
-
- 29 3月, 2004 1 次提交
-
-
由 Richard Levitte 提交于
make update
-
- 26 3月, 2004 1 次提交
-
-
由 Richard Levitte 提交于
the symbol name).
-
- 13 2月, 2003 1 次提交
-
-
由 Richard Levitte 提交于
-
- 11 8月, 2002 2 次提交
-
-
由 Richard Levitte 提交于
casing.
-
由 Richard Levitte 提交于
-
- 10 8月, 2002 1 次提交
-
-
由 Richard Levitte 提交于
-
- 19 7月, 2002 1 次提交
-
-
由 Richard Levitte 提交于
-
- 17 7月, 2002 1 次提交
-
-
由 Richard Levitte 提交于
PR: 124
-
- 23 5月, 2002 1 次提交
-
-
由 Richard Levitte 提交于
-
- 28 2月, 2002 1 次提交
-
-
由 Richard Levitte 提交于
-
- 24 1月, 2002 1 次提交
-
-
由 Richard Levitte 提交于
more.
-
- 25 10月, 2001 1 次提交
-
-
由 Richard Levitte 提交于
libdes (which is still used out there) or other des implementations, the OpenSSL DES functions are renamed to begin with DES_ instead of des_. Compatibility routines are provided and declared by including openssl/des_old.h. Those declarations are the same as were in des.h when the OpenSSL project started, which is exactly how libdes looked at that time, and hopefully still looks today. The compatibility functions will be removed in some future release, at the latest in version 1.0.
-
- 02 10月, 2001 1 次提交
-
-
由 Richard Levitte 提交于
-
- 14 5月, 2001 1 次提交
-
-
由 Richard Levitte 提交于
characters.
-
- 09 3月, 2001 1 次提交
-
-
由 Richard Levitte 提交于
-
- 22 2月, 2001 1 次提交
-
-
由 Richard Levitte 提交于
there's no point creating an alias for it.
-
- 20 2月, 2001 2 次提交
-
-
由 Richard Levitte 提交于
OCSP_CRLID_new and OCSP_crlID_new clash on case-insensitive systems.
-
由 Richard Levitte 提交于
missed any. This compiles and runs on Linux, and external applications have no problems with it. The definite test will be to build this on VMS.
-