[openssl.org #1273] [PATCH] support for SEED (RFC4269)

2006-08-11 Thread via RT
[EMAIL PROTECTED] - Sat Jan 21 19:39:13 2006]: SEED is a 128-bit block cipher registered to ISO/IEC and IETF and has some applications already (RFC4010: CMS, RFC4162: TLS, RFC4196: IPSec). More detailed information on the algorithm is available in RFC4269. I just updated the patch for

Re: OpenSSL 0.9.8b - DTLS1 bug

2006-08-11 Thread Kyle Hamilton
As I recall, it was someone who was working on it who was having patches committed as he implemented it, and never finished it? It probably is buggy. -Kyle H On 8/10/06, ViSolve Security Consulting Group [EMAIL PROTECTED] wrote: Hi Developers, We have compiled OpenSSL 0.9.8b on HP-UX

Re: OpenSSL 0.9.8b - DTLS1 bug

2006-08-11 Thread authesserre samuel
Hi, This implementation is totally wrong (I posted a complete list of problems I've found), this implementation doesn't follow the rfc at all but works on my Debian box to see where the problem comes from you could use Wireshark (new version of Ethereal) I have made a dissector that allow you to

OPENSSL_gmtime on platforms that don't have a safe gmtime function

2006-08-11 Thread Joe Gluck
The OPENSSL_gmtime in o_time.c (that gets called from other places like ASN1_UTCTIME_cmp_time_t in a_utctm.c) does not use the safe version of gmtime in lots of platforms including:OPENSSL_SYS_WIN32OPENSSL_SYS_OS2 __CYGWIN32__OPENSSL_SYS_MACOSXOPENSSL_SYS_SUNOS This could cause problems in

RE: OPENSSL_gmtime on platforms that don't have a safe gmtime function

2006-08-11 Thread David Schwartz
The OPENSSL_gmtime in o_time.c (that gets called from other places like ASN1_UTCTIME_cmp_time_t in a_utctm.c) does not use the safe version of gmtime in lots of platforms including: OPENSSL_SYS_WIN32 OPENSSL_SYS_OS2 __CYGWIN32__ OPENSSL_SYS_MACOSX OPENSSL_SYS_SUNOS This could cause problems in