TSU Notification - encryption was Re: [openssl.org #1336] OpenSSL support for Kerberos

__ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]

[openssl.org #1112] 0.9.8 beta 5 build issue on windows

The following build issue exists: cl /Fotmp32dll\c_zlib.obj -Iinc32 -Itmp32dll -DZLIB_SHARED -DZLIB -DKRB5_MIT /MD /W3 /WX /G5 /Ox /O2 /Ob2 /Gs0 /GF /Gy /nologo -DOPENSSL_SYSNAME_WIN32 -DWIN32_LEAN_AND_MEAN -DL_ENDIAN -DDSO_WIN32 -DOPENSSL_SYSNAME_WINNT -DOPENSSL_USE_APPLINK -I.

[openssl.org #807] 0.9.7 snapshot patches for compilation on Windows

__ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]

[openssl.org #806] 0.9.8 snapshot patches for compilation on Windows

__ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]

[openssl.org #753] 0.9.6l does not compile on Windows

The inclusion of e_os.h in crypto\des\cfb_enc.c must be specified as either #include openssl/e_os.h or #include ../e_os.h This is not performed in a consistent manner in OpenSSL 0.9.6. __ OpenSSL Project

[openssl.org #392] X509_STORE_CTX_cleanup 0.9.7 beta 5

I'm tracking down the cause of an exception that did not occur with Kermit 95 with previous 0.9.7 builds. In the process I noticed that in X509_STORE_CTX_cleanup the buffer ctx-ex_data is freed with CRYPTO_free_ex_data prior to it being cleansed with OPENSSL_cleanse I'm pretty sure

[openssl.org #393] 0.9.7 beta 5 crypto/x509/x509_vfy.c X509_STORE_CTX_init() memset required

Please ignore my previous e-mail, the problem is located in X509_STORE_CTX_init() The memset((ctx-ex_data),0,sizeof(CRYPTO_EX_DATA)) that was commented out needs to be restored due to the use of OPENSSL_cleanse() on that data structure. In previous releases this data structure would have

[openssl.org #367] s3_clnt.c ssl3_get_server_hello and SSL_SESSION cipher_id 0.9.7-b4

Sometime in the last couple of weeks the following change was made to s3_clnt.c 698,699c699 if (s-hit (s-session-cipher != c)) --- if (s-hit (s-session-cipher_id != c-id)) The only problem is that at this point in time the cipher_id field of the SSL_SESSION has not been set.

[openssl.org #360] crypto/dsa/dsa_lib.c DSA_size()

What is the appropriate size for 'buf' in DSA_size()? 4 bytes is certainly not correct. My guess is that we want to support at least 256 bits and so it needs to be at least 32 bytes. Does anyone have a better recommendation? Jeffrey Altman * Volunteer Developer Kermit 95 2.1 GUI

[openssl.org #361] Re: OpenSSL and compression using ZLIB

http://www.ietf.org/internet-drafts/draft-ietf-tls-compression-03.txt defines the compression numbers to be: enum { null(0), ZLIB(1), LZS(2), (255) } CompressionMethod; Therefore proposed numbers have been issued. I suggest that OpenSSL define the CompressionMethod numbers to be: enum

Re: [openssl.org #360] crypto/dsa/dsa_lib.c DSA_size()

other bytes could not be touched in the future though. In message [EMAIL PROTECTED] on Mon, 25 Nov 2002 09:32:30 +0100 (MET), Jeffrey Altman via RT [EMAIL PROTECTED] said: rt rt What is the appropriate size for 'buf' in DSA_size()? rt rt 4 bytes is certainly not correct. My guess

Re: [openssl.org #360] crypto/dsa/dsa_lib.c DSA_size()

Then the assertion should be removed because as it is now it will always fail. Jeffrey Altman wrote: The code is the same in both 0.9.6- and 0.9.7-beta4. in 0.9.7-b4 there is an assertion added that is being triggered because the buf size is considered too small. However, tracing

Re: [openssl.org #189] Kerberos Ciphersuite IDs

Richard: Just tried to build this and it fails: .\ssl\s3_lib.c(609) : error C2065: 'SSL3_TXT_KRB5_DES_192_CBC3_MD5' : undeclared identifier .\ssl\s3_lib.c(609) : error C2099: initializer is not a constant .\ssl\s3_lib.c(610) : warning C4047: 'initializing' : 'const char *' differs in levels of

Re: [openssl.org #189] Kerberos Ciphersuite IDs

I believe these patches correct the problem: *** \ssl\tmp\ssl3.h Thu Oct 10 05:04:18 2002 --- ssl3.h Tue Oct 15 14:01:42 2002 *** *** 215,234 #define SSL3_TXT_FZA_DMS_FZA_SHA FZA-FZA-CBC-SHA #define SSL3_TXT_FZA_DMS_RC4_SHA FZA-RC4-SHA #define

[openssl.org #169] 0.9.7-b3 compile error on Win32

ssl\s3_srver.c (1591) error: pms_length is not a member of evp_cipher_st I believe the correct reference is if (enc_pms.length sizeof pms) instead of if (enc.pms_length sizeof pms) Jeffrey Altman * Sr.Software Designer Kermit 95 2.0 GUI available now!!! The Kermit Project @

Re: [openssl.org #170] OpenSSLDie not exported in Win32

OK, I don't understand why it needs to be exported - isn't it internal to the library? But assuming it does, I prefer the original suggestions (i.e. move the declaration of OpenSSLDie()). It needs to be exported because the function is defined in libeay32.dll and used in ssleay32.dll on

Re: [openssl.org #170] OpenSSLDie not exported in Win32

jaltman Now the choices as I see it are: jaltman jaltman . export the function. which I have done in order to get the jaltmancode to compile and link on Windows, or jaltman jaltman . remove the call entirely and instead simply have OpenSSL return jaltmanan error to the

Re: [openssl.org #170] OpenSSLDie not exported in Win32

In message [EMAIL PROTECTED] on Tue, 30 Jul 2002 11:31:17 EDT, Jeffrey Altman [EMAIL PROTECTED] said: jaltman since they do not compile on two major platforms. On VMS, creating OpenSSL shared libraries is not the norm yet, so it'll build fine :-). fine. shared libraries won't work on