OpenSSL infrastructure migration

2013-01-15 Thread Lutz Jaenicke
Hi! As you will already have noted, the OpenSSL project is currently moving its infrastructure to a new server. This migration is combined with a change and/or upgrade of the tools (CVS - GIT, RT 3.x - 4.x, ...) so we have decided to set up the new server first and to perform a step by step

Re: OpenSSL infrastructure migration

2013-01-15 Thread Lutz Jaenicke
On 01/15/2013 12:50 PM, Lutz Jaenicke wrote: Hi! As you will already have noted, the OpenSSL project is currently moving its infrastructure to a new server. This migration is combined with a change and/or upgrade of the tools (CVS - GIT, RT 3.x - 4.x, ...) so we have decided to set up the

Re: OpenSSL infrastructure migration

2013-01-15 Thread Lutz Jaenicke
On 01/15/2013 12:50 PM, Lutz Jaenicke wrote: Hi! As you will already have noted, the OpenSSL project is currently moving its infrastructure to a new server. This migration is combined with a change and/or upgrade of the tools (CVS - GIT, RT 3.x - 4.x, ...) so we have decided to set up the

[openssl.org #2956] incomplete archive

2013-01-15 Thread Geoffrey Jones via RT
The archive of the sample application at http://openssl.com/fips/2.0/platforms/ios/fips-pi.tar.gz is incomplete or corrupted. smime.p7s Description: S/MIME cryptographic signature

Windows 8 ARM compilation - OPENSLL_UplinkTable

2013-01-15 Thread Gopakumar Pillai
I am trying to compile OpenSSL 0.9.8x for Windows 8 ARM platform. Basically want SSL to work on Windows 8 ARM tablets. My main issue is because of unresolved symbol for OPENSSL_UplinkTable. Looking at the scripts and code, I see that there's no support for ARM assembly (in uplink.pl

Re: Committing to openSSL - maximum fragment length

2013-01-15 Thread Lutz Jaenicke
On 01/12/2013 01:26 PM, Attila Gulyas wrote: Hi, I have been working on implementing Maximm fragmentation length extension (RFC3546, obsoleted by RFC6066) and I'd like to commit my work so that it'd be available in later editions of openssl. How may I do that? (I've been looking for an

[openssl.org #2957] genpkey for DH key generation does not honor recommended private length

2013-01-15 Thread Ron Harvey via RT
Greetings, When using 'genpkey' command to generate DH keys, the 'recommended private key size' is not honored when it is present in the DH Parameters file. I found this problem in 1.0.1c. Consider the attached parameter file, openssl_dh_params.pem $ openssl dhparam -in openssl_dh_params.pem