__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
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. /Fdout3
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
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
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
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
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 b
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, trac
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 D
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 {
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 availa
The following minor problems need to be corrected in 0.9.7 b4 compiled
against the MIT Kerberos distribution:
diff -cw openssl-0.9.7-beta4\ssl/kssl.h openssl-0.9.7-beta4-modified\ssl/kssl.h
*** openssl-0.9.7-beta4\ssl/kssl.h Tue Nov 12 08:23:26 2002
--- openssl-0.9.7-beta4-modified\ssl/kssl.h Tue
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"
#defin
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
The problem with the OpenSSLDie() function is not that it is not being
exported. The problem is that it calls abort() which terminates the
application that is using OpenSSL as a library. This opens up a
wonderful denial of service attack. That is what Arne Ansper started
to address with his p
> 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
> jaltman> Now the choices as I see it are:
> jaltman>
> jaltman> . export the function. which I have done in order to get the
> jaltman>code to compile and link on Windows, or
> jaltman>
> jaltman> . remove the call entirely and instead simply have OpenSSL return
> jaltman>an error
> 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
Need to add it to the exports list.
Jeffrey Altman * Sr.Software Designer Kermit 95 2.0 GUI available now!!!
The Kermit Project @ Columbia University SSH, Secure Telnet, Secure FTP, HTTP
http://www.kermit-project.org/Secured with MIT Kerberos, SRP, and
[EMAIL PROTECTED]
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
21 matches
Mail list logo
