[openssl.org #1648] DTLS and Winsock timeouts bug

2008-03-07 Thread Pavel via RT
Hello, When you try to establish DTLS connection you should use timeouts as said in RFC. DTLS uses socket's timeouts. Windows sockets have some differences in timeout API, but DTLS does not consider them. So when you set timeouts with BIO_ctrl() and BIO_CTRL_DGRAM_SET_RECV_TIMEOUT or

[openssl.org #1649] openssl-fips-test-1.2.0 bug

2008-03-07 Thread qianbohound via RT
Hi Openssl Developers, I may find one bug for openssl-fips-test-1.2.0 which is downloaded from ftp://ftp.openssl.org/snapshot/ The machine I used is: [EMAIL PROTECTED] uname -a HP-UX sshpa6 B.11.31 U 9000/800 2404418693 unlimited-user license The steps to reproduct the bug are as

RE: Install openssl-0.9.8g on a Mac OS X PPC server

2008-03-07 Thread Zhao, Wenzhong, Dr {Zhao}(GSFC-613.2)[SSAI]
Dear Z, You have a very good point. Could you show me how to change configure file or Makefile to accomplish this? Thanks, Wenzhong -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, March 04, 2008 1:56 PM To:

RE: Install openssl-0.9.8g on a Mac OS X PPC server

2008-03-07 Thread Ted Mittelstaedt
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Zhao, Wenzhong, Dr {Zhao}(GSFC-613.2)[SSAI] Sent: Monday, March 03, 2008 7:52 PM To: openssl-dev@openssl.org Cc: [EMAIL PROTECTED] Subject: Install openssl-0.9.8g on a Mac OS X PPC server Hi,

[openssl.org #1650] signature length in ECDSA

2008-03-07 Thread JP Szikora via RT
Hi, I try to understand why the signature length is variable in ECDSA. Normally with 160bits EC, it must be 46 bytes long: 20 bytes for each of the 2 components and 4 + 2 bytes for ASN.1. I think it must be a bug in the ASN.1 creation of the signature. Here is the details: I'm testing this

Re: [openssl.org #1650] signature length in ECDSA

2008-03-07 Thread Mounir IDRASSI
Hi, This is due to the fact that the integers are stored as unsigned. So, when the MSB of a computed value is set, the encoding adds an extra 0x00 to its ASN.1 representation. This is normal and it explains what you are experiencing. Cheers, Mounir IDRASSI IDRIX - Cryptography And IT Security