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
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
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
In message [EMAIL PROTECTED] on Tue, 15 Oct 2002 19:55:14
+0200 (METDST), Jeffrey Altman via RT [EMAIL PROTECTED] said:
Thanks for identifying the typos, I just committed an appropriate
change (I hope). Please check the next snapshot.
rt Just tried to build this and it fails:
rt
rt
In message [EMAIL PROTECTED] on Tue, 15 Oct 2002 19:55:14
+0200 (METDST), Jeffrey Altman via RT [EMAIL PROTECTED] said:
Thanks for identifying the typos, I just committed an appropriate
change (I hope). Please check the next snapshot.
rt Just tried to build this and it fails:
rt
rt
There, I finally got the time to put this in. Just commited.
Please test the next 0.9.7 snapshot and make sure I got it all right.
This ticket is now resolved.
[[EMAIL PROTECTED] - Mon Sep 30 18:55:14 2002]:
Any chance of making progress on this?
As a reminder, the issue is that the
In message [EMAIL PROTECTED] on Mon, 30 Sep 2002 18:55:16
+0200 (METDST), Andreas Sterbenz via RT [EMAIL PROTECTED] said:
rt
rt Any chance of making progress on this?
rt
rt As a reminder, the issue is that the Kerberos ciphersuites in OpenSSL do
rt not use the IDs defined in RFC2712, which
In message [EMAIL PROTECTED] on Mon, 30 Sep 2002 18:55:16
+0200 (METDST), Andreas Sterbenz via RT [EMAIL PROTECTED] said:
rt
rt Any chance of making progress on this?
rt
rt As a reminder, the issue is that the Kerberos ciphersuites in OpenSSL do
rt not use the IDs defined in RFC2712, which
Any chance of making progress on this?
As a reminder, the issue is that the Kerberos ciphersuites in OpenSSL do
not use the IDs defined in RFC2712, which obviously has negative effects
on interoperability.
Thanks,
Andreas.
Forwarding this message from ietf-tls.
As mentioned before, I agree with the suggested fix (do not use this
ciphersuite).
Andreas.
Original Message
Subject: [ietf-tls] Re: Ciphersuite 0x00 0x1e
Date: Fri, 09 Aug 2002 19:21:33 +
From: David Hopwood [EMAIL PROTECTED]
resubmitting via RT. The absence of a quick reply leads me to believe
that there is indeed something wrong. I encourage you too look at this
before 0.9.7 release, otherwise we will run into serious
interoperability problems in the future.
Andreas.
Original Message
Subject:
Hmm, there's a problem that haven't been addressed at all by the
IETF. SSLv3 contains the following as part of it's ciphersuite:
The final cipher suites are for the FORTEZZA token.
CipherSuite SSL_FORTEZZA_KEA_WITH_NULL_SHA = {
0X00,0X1C };
CipherSuite
Richard Levitte via RT wrote:
Hmm, there's a problem that haven't been addressed at all by the
IETF. SSLv3 contains the following as part of it's ciphersuite:
The final cipher suites are for the FORTEZZA token.
CipherSuite SSL_FORTEZZA_KEA_WITH_NULL_SHA = {
0X00,0X1C
Has anyone sent a query to Win Treese [EMAIL PROTECTED] [TLS WG chair]
and perhaps the area directors looking for guidance?
The TLS Protocol Version 1.0 is in the process of being re-issued:
http://www.ietf.org/internet-drafts/draft-ietf-tls-rfc2246-bis-01.txt
and clearly this problem should
14 matches
Mail list logo
