Re: DTLSv1_listen unable to accept second client on windows (This works on Linux)

2011-07-18 Thread Michael Tüxen
Hi Nilesh, thank you very much for isolating the problem in the socket handling and providing a small test program. Let us have a look (it might take some time). Best regards Michael On Jul 19, 2011, at 2:56 AM, Nilesh Vaghela wrote: > Hi Michael and Robin, > > I verified the same problem WITHO

Re: openssl md5 output

2011-07-18 Thread Wim Lewis
On 18 Jul 2011, at 1:25 PM, Patrick Donnelly wrote: > Are you seriously suggesting that parsing the md5sums of multiple > files from the output of "openssl md5 *.txt" is a sensible use case? It's not just sensible, it's fairly common. The DIGEST(filename)=hexhexhex... output style is in imitatio

Re: openssl md5 output

2011-07-18 Thread Coda Highland
>> To answer your initial question, consider the case of "$ openssl md5 >> *.txt", where each line needs to have that information. The new format >> makes the output consistent regardless of manner of implementation, >> which from a future-proofing standpoint makes more sense than changing >> the o

Re: openssl md5 output

2011-07-18 Thread Patrick Donnelly
On Mon, Jul 18, 2011 at 4:05 PM, Coda Highland wrote: > On Mon, Jul 18, 2011 at 2:41 PM, Patrick Donnelly > wrote: >> Why does this command prepend useless redundant information? >> >> $ openssl md5 <(echo foo) >> MD5(/dev/fd/63)= d3b07384d113edec49eaa6238ad5ff00 > > --snip-- > >> Thank you *so*

Re: openssl md5 output

2011-07-18 Thread Coda Highland
On Mon, Jul 18, 2011 at 2:41 PM, Patrick Donnelly wrote: > Why does this command prepend useless redundant information? > > $ openssl md5 <(echo foo) > MD5(/dev/fd/63)= d3b07384d113edec49eaa6238ad5ff00 --snip-- > Thank you *so* much. I would have framed this email more politely but > you have su

openssl md5 output

2011-07-18 Thread Patrick Donnelly
Why does this command prepend useless redundant information? $ openssl md5 <(echo foo) MD5(/dev/fd/63)= d3b07384d113edec49eaa6238ad5ff00 ^ ^ I just cannot fathom why this was done. This is just all around terrible design. Not only is this information redundant and entirely worthles

Re: [openssl.org #2553] [Bug report] SIGILL on sparc64 (linux/solaris)

2011-07-18 Thread BERTRAND Joel via RT
Andy Polyakov via RT a écrit : I see a very strange bug in crypto/sparcv9cap.c. OpenSSL 1.0.0d checks sparc capabilities with SIGILL signal. On sparc64 (both Linux and solaris, with UltraSPARC III+ and T1 CPU's), SIGILL handler is called and program terminates with SIGILL in

Re: DTLSv1_listen unable to accept second client on windows (This works on Linux)

2011-07-18 Thread Michael Tüxen
On Jul 18, 2011, at 5:18 PM, Yogesh Chopra wrote: > Hi, > I am using a separate (second socket) for client connect and > leaving the listening socket unconnected to receive everything else. > (The server program is same as provided for linux earlier). The server > program is same as provided ear

Re: [openssl.org #2553] [Bug report] SIGILL on sparc64 (linux/solaris)

2011-07-18 Thread Andy Polyakov via RT
>>> I see a very strange bug in crypto/sparcv9cap.c. OpenSSL 1.0.0d checks >>> sparc capabilities with SIGILL signal. On sparc64 (both Linux and >>> solaris, with UltraSPARC III+ and T1 CPU's), SIGILL handler is called >>> and program terminates with SIGILL in _sparcv9_fmadd_probe: >>> >>>

Re: DTLSv1_listen unable to accept second client on windows (This works on Linux)

2011-07-18 Thread Yogesh Chopra
Hi, I am using a separate (second socket) for client connect and leaving the listening socket unconnected to receive everything else. (The server program is same as provided for linux earlier). The server program is same as provided earlier. (This will need modifications for windows and I will t

Re: [openssl.org #2553] [Bug report] SIGILL on sparc64 (linux/solaris)

2011-07-18 Thread BERTRAND Joel via RT
Andy Polyakov via RT a écrit : > Hi, Hello, >> I see a very strange bug in crypto/sparcv9cap.c. OpenSSL 1.0.0d checks >> sparc capabilities with SIGILL signal. On sparc64 (both Linux and >> solaris, with UltraSPARC III+ and T1 CPU's), SIGILL handler is called >> and program terminate

Re: openssl compilation for WinCE

2011-07-18 Thread Pierre DELAAGE
Hello, All the answers to your questions are here : http://delaage.pierre.free.fr/ good luck Pierre Delaage Le 14/07/2011 14:40, Kchitiz Saxena a écrit : Hi I am trying to compile openssl version 0.9.8p for Win CE 5.0 (Armv4i). I am using Microsoft embedded VC++ 4.0 for the same. I followed t

Re: [openssl.org #2553] [Bug report] SIGILL on sparc64 (linux/solaris)

2011-07-18 Thread Andy Polyakov via RT
Hi, > I see a very strange bug in crypto/sparcv9cap.c. OpenSSL 1.0.0d checks > sparc capabilities with SIGILL signal. On sparc64 (both Linux and > solaris, with UltraSPARC III+ and T1 CPU's), SIGILL handler is called > and program terminates with SIGILL in _sparcv9_fmadd_probe: > > 0

[openssl.org #2565] More tolerant detection of XMPP starttls sequence

2011-07-18 Thread Tomas Mraz via RT
The attached patch written by J.H.M Ray Dassen improves detection of the XMPP starttls sequence for s_client. Please consider applying it. -- Tomas Mraz No matter how far down the wrong road you've gone, turn back. Turkish proverb diff -ru openssl-1.

[openssl.org #2564] PKCS7_cert_from_signer_info Enhancement Request

2011-07-18 Thread Ludovic FLAMENT via RT
Hi, I just find (after spending some time on debug) than the PKCS7_cert_from_signer_info functions doesn't work in case of Signed and enveloped PKCS7 As I don't see any reason of that, I would propose a support of this case. Actual version (Openssl 1.0.0d) :

Re: Which tar.gz file I need for OpenSSL FIPS Object Module?

2011-07-18 Thread Kyle Hamilton
The Security Policy is the document you need. Please see Steve Marquess's link to the official copy at NIST. The Security Policy explains everything, including what file you need to obtain, its HMAC, how to verify it, what you must do to retain validation of the canister, how to build the caniste