On 05/13/2011 02:21 PM, John Foley wrote:
> It looks like TLS 1.2 is being implemented in recent commits. Is there
> an anticipated completion date for when v1.2 will be fully implemented?
TLS 1.2 is being implemented in two stages. The first phase will be
completed in a few weeks. The schedule
I've now tested both Francis Dupont's original patch and Jung-uk Kim's
replacement. Both patches work for my test case (make test with the
rpki.net Python code), both on FreeBSD 8.2-STABLE (with gcc 4.6 and
binutils from ports, to get new enough tools to show the problem with
the unpatched code) a
On Fri, May 13, 2011 at 12:24:25PM -0400, Steve Marquess wrote:
> > What is happening?
> >
> > No Fips in the Openssl 1.0.1 STABLe.
> >
> >
>
> Correct, and you won't be seeing the "FIPS capable" support there for
> some time. We're concentrating on the validation of the module (OpenSSL
> FIPS Ob
It looks like TLS 1.2 is being implemented in recent commits. Is there
an anticipated completion date for when v1.2 will be fully implemented?
__
OpenSSL Project http://www.openssl.org
Development M
On Fri, May 13, 2011, The Doctor wrote:
> What is happening?
>
> No Fips in the Openssl 1.0.1 STABLe.
>
It never was in 1.0.1-stable. A bug with the snapshot generation meant that
HEAD was incorrectly being tared as 1.0.1 in shapshots in fact it was
tared as 1.0.0 and 0.9.8 too. That is fixed n
> OK, I'm still a bit confused on the version labeling. Is it safe to
> assume the next stable label pulled off HEAD (e.g. 1.0.2) will include
> support for "make -f Makefile.fips dist". Or to put the question
> another way, what stable label should be used to generate the FIPS
> Object Model 2.0
OK, I'm still a bit confused on the version labeling. Is it safe to
assume the next stable label pulled off HEAD (e.g. 1.0.2) will include
support for "make -f Makefile.fips dist". Or to put the question
another way, what stable label should be used to generate the FIPS
Object Model 2.0 source co
> Steve,
>
> It looks like the FIPS 2.0 code has been going into HEAD. When do you
> plan to pull a branch for the FIPS Object Model 2.0?
We don't. The source tarball for the eventual validated module will be
generated with "make -f Makefile.fips dist" which extracts the relevant
subset of code.
Steve,
It looks like the FIPS 2.0 code has been going into HEAD. When do you
plan to pull a branch for the FIPS Object Model 2.0?
On 05/13/2011 12:24 PM, Steve Marquess wrote:
> > What is happening?
>
> >
>
> > No Fips in the Openssl 1.0.1 STABLe.
>
> >
>
> >
>
> Correct, and you won't be seei
> What is happening?
>
> No Fips in the Openssl 1.0.1 STABLe.
>
>
Correct, and you won't be seeing the "FIPS capable" support there for
some time. We're concentrating on the validation of the module (OpenSSL
FIPS Object Module 2.0) now.
-Steve M.
--
Steve Marquess
OpenSSL Software Foundation,
What is happening?
No Fips in the Openssl 1.0.1 STABLe.
--
Member - Liberal International This is doc...@nl2k.ab.ca Ici doc...@nl2k.ab.ca
God, Queen and country! Never Satan President Republic! Beware AntiChrist
rising!
http://twitter.com/rootnl2k http://www.facebook.com/dyadallee
Stop Steph
On 5/11/2011 4:08 PM, Technical Support wrote:
Steve
One of our Army clients (USAMITC) is asking if we know of any Unix based SSH
client and or server which will support CAC certificate based authentication
other then Tectia. Are you aware of any?
Have a look at the OpenSC page.
http://www.
Attached is a file against today's CVS that adds the new AES XTS modes
to the lookup table (OpenSSL_add_all_ciphers).
Regards,
Alex Hornung
Index: crypto/evp/c_allc.c
===
RCS file: /v/openssl/cvs/openssl/crypto/evp/c_allc.c,v
retriev
13 matches
Mail list logo
