Hi all,
does anybody know if there are downloadable binaries of openssl-fips
and/or openssl-fips-ecp (2.0.16 or earlier) for Windows ?
Cheers,
Max
--
Best Regards,
Massimiliano Pala, Ph.D.
OpenCA Labs Director
OpenCA Logo
smime.p7s
Description: S/MIME Cryptographic Signature
--
openssl-use
On 07/12/17 16:55, Porter, Andrew wrote:
> My "make test" for today's 1.0.2n release is getting an error at the very
> last (I think)
> "test_bad_dtls" step. This is FIPS-enabled, built with the 2.0.12 FIPS
> module. With the
> Previous 1.0.2m release the "test_bad_dtls" step silently completed
> On Dec 7, 2017, at 8:55 AM, OpenSSL wrote:
>
> OpenSSL - The Open Source toolkit for SSL/TLS
> https://www.openssl.org/
>
> The OpenSSL project team is pleased to announce the release of
> version 1.0.2n of our open source toolkit for SSL/TLS. For details
> of changes and known iss
My "make test" for today's 1.0.2n release is getting an error at the very last
(I think)
"test_bad_dtls" step. This is FIPS-enabled, built with the 2.0.12 FIPS module.
With the
Previous 1.0.2m release the "test_bad_dtls" step silently completed but with
1.0.2n I get:
test_bad_dtls
../util/shlib
On 07/12/2017 15:05, Michael Wojcik wrote:
From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
Of Jakob Bohm
Sent: Thursday, December 07, 2017 08:41
To: openssl-users@openssl.org
And I would still say that "consult a lawyer" is a useless answer,
especially as most OpenSSL us
➢ The OP claimed the file was only in the FIPS tarballs, and not in the
OpenSSL tarballs. My questions were based on that.
So the OP is wrong.
➢ Saying "in the distribution and website" is also quite vague and
thus another example of a non-answer.
No it’s not. The OpenSSL dist
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
> Of Jakob Bohm
> Sent: Thursday, December 07, 2017 08:41
> To: openssl-users@openssl.org
>
> And I would still say that "consult a lawyer" is a useless answer,
> especially as most OpenSSL users will be in the same legal s
=
URL for this Security Advisory:
https://www.openssl.org/news/secadv/20171207.txt
Note: the online version of the advisory may be updated with additional details
over time.
For details of OpenSSL severity classifications please see:
https://www.openssl.org/policies/secpolicy.html
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 1.0.2n released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.0.2n of our open sour
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
> Of Jakob Bohm
> Sent: Thursday, December 07, 2017 01:44
> >
> Actually in some of my code, I have found that the callback can
> still be useful by examining the SSL session argument to
> heuristically identify likely clien
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
> Of Salz, Rich via openssl-users
> Sent: Wednesday, December 06, 2017 15:22
>
> ➢Or at least that used to be the case. TLSv1.3 got rid of renegotiation,
> so if
> you have a TLSv1.3 connection, it will never renegotia
On 07/12/2017 13:39, Salz, Rich via openssl-users wrote:
README.ECC has never been part of 1.0.2 and is always part of the the 1.1.0
tarballs; do you have evidence otherwise?
I don’t think the team is going to answer any questions beyond what is already
in the distrubtuion and website except t
README.ECC has never been part of 1.0.2 and is always part of the the 1.1.0
tarballs; do you have evidence otherwise?
I don’t think the team is going to answer any questions beyond what is already
in the distrubtuion and website except to say that the license is NOT limited
to the FIPS releases
Hi all,
On a project I am working on we are wrestling with the problem of
preventing discovery of the private key, in a consumer device. I have been
advocating the use of the ENGINE API as a general model which can be used
to provide the best isolation possible on the customer's chosen hardware:
Hi,
On 04/12/17 09:10, wizard2...@gmail.com wrote:
Hi ,
Please see in attach the files that I'm using.
I've just taken a look at your certificates and they've not been
generated correctly:
$ openssl x509 -subject -issuer -noout -in ca.crt -dates -serial
subject= /C=AU/ST=Some-State/O=Inter
On 07/12/17 04:38, Oliver Niebuhr wrote:
> BTW: It turned out that the VS SSA-Optimizer is at fault here! After
> disabling it with '/d2SSAOptimizer-' blake2b.c compiles fine.
>
> Seems like a Bug with this Tool Set Version.
>
> I created a BR:
> https://github.com/openssl/openssl/issues/4859
>
>
16 matches
Mail list logo
