Hi,
I'm not subscribed so please CC me on responses.
At http://www.openssl.org/docs/fips/fipsvalidation.html it mentions that
the formal award of the new validation certificate was Feb 2012. That
date is now passed, has the certificate been awarded or do we have a new
estimate for
Hi
I have a keyfile and password and I use the
PEM_read_PrivateKey( FILE* f, EVP_PKEY**pkey, pem_password_cb, pwd )
to read the private key
but the API crashes on windows.
There have been previous threads that makes use of the API below with NULL
arguments
Same issue has been reported and resolved in #1624.
This report can be closed.
Dan
__
OpenSSL Project http://www.openssl.org
Development Mailing List
The OpenSSL FIPS Object Module 2.0 is now in coordination status at
the CMVP. That's usually a good sign that the formal validation award
is imminent (as in a week or three...).
-Steve M.
--
Steve Marquess
OpenSSL Software Foundation, Inc.
1829 Mount Ephraim Road
Adamstown, MD 21710
USA
+1
Same problem apply for cross-certificates which create multiple paths also.
Imagine the expiring CA (expiring within year or two, not expired
already). The organization will create the new one, but want to maintain
transition period for the users. So create two cross certificates - the
public
Hello Steve,
Will the new certificate support that is has been tested in a Windows 7
configuration?
Michelle
-Original Message-
From: owner-openssl-...@openssl.org [mailto:owner-openssl-...@openssl.org]
On Behalf Of Steve Marquess
Sent: Tuesday, March 06, 2012 5:09 AM
To:
On 03/06/2012 08:49 AM, Vanden, Michelle CTR USAF AFMC AAC/EBYC wrote:
Hello Steve,
Will the new certificate support that is has been tested in a Windows 7
That validation will include the following MS Windows platforms:
Windows 7 32bit on x86, SSE2 optimization
Windows 7
Steve
Thats where the entire fips validation really breaks down. Complete end user
confusion on what machine, operating system and processer type can and cannot
be used. It must be a real deployment stumbling block for large organizations.
Ken
InterSoft International, Inc.
Voice:
On 03/06/2012 09:55 AM, Technical Support wrote:
Steve
Thats where the entire fips validation really breaks down. Complete end
user confusion on what machine, operating system and processer type can
and cannot be used. It must be a real deployment stumbling block for
large organizations.
[seggelm...@fh-muenster.de - Mon Mar 05 15:26:38 2012]:
The DTLS implementation does not lower the assumed MTU after
unsuccessful retransmissions, which results in a failing handshake in
case fragmentation is necessary.
With this patch the MTU is reduced to a safe value of 576 - 20 - 8
I'm figuring this out as I go along, but there's a lot of unknown before me,
so I'm looking for any general wisdom, experience, or advice you guys might
offer. Ultimately, the reason I'm doing what I'm doing is academic. Maybe
I'll be doing actually useful work, but that's not the point. The
On 3/6/2012 8:43 AM, Steve Marquess wrote:
On 03/06/2012 08:49 AM, Vanden, Michelle CTR USAF AFMC AAC/EBYC wrote:
Hello Steve,
Will the new certificate support that is has been tested in a Windows 7
That validation will include the following MS Windows platforms:
Windows 7 32bit on
On 03/06/2012 06:47 PM, William A. Rowe Jr. wrote:
On 3/6/2012 8:43 AM, Steve Marquess wrote:
On 03/06/2012 08:49 AM, Vanden, Michelle CTR USAF AFMC AAC/EBYC wrote:
Hello Steve,
Will the new certificate support that is has been tested in a Windows 7
That validation will include the
13 matches
Mail list logo
