On 09/01/2016 08:22 AM, Jakob Bohm wrote:
> Dear OpenSSL team,
>
> Given the recent patent lawsuit between RIM/CertiCom and Avaya
> mentioning the ECC code in OpenSSL, what is (according to the
> OpenSSL team) the patent status of the ECC code in OpenSSL?
>
> Specifically:
>
> - Was the OpenSSL
It's hard to answer these questions without wandering down the "legal advice"
alleyway.
I think Steve's post answered your questions.
> >> - Was the OpenSSL ECC code provided under a still-valid patent
> >> license from someone in the power to grant it, perhaps Sun
> >> (now Oracle
On 01/09/2016 20:11, Steve Marquess wrote:
On 09/01/2016 08:22 AM, Jakob Bohm wrote:
Dear OpenSSL team,
Given the recent patent lawsuit between RIM/CertiCom and Avaya
mentioning the ECC code in OpenSSL, what is (according to the
OpenSSL team) the patent status of the ECC code in OpenSSL?
On 31/08/16 17:42, Kjetil Birkeland Moe wrote:
> Dear all,
> I have turned to /s_time/ to evaluate the performance of a local Nginx
> server setup, but seems to immediately run into problems that do not
> appear when using /s_client/.
>
> Server setup is largely based on recommendations from
> Am I missing something here?
OpenSSL 1.1.0 does not support FIPS. It's in the README.FIPS file :)
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Many thanks Mounir, this is what I swa looking for.
--
View this message in context:
http://openssl.6102.n7.nabble.com/RSA-sign-using-SHA256-with-mgf1-padding-tp68101p68152.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
--
openssl-users mailing list
To unsubscribe:
Dear OpenSSL community,
I have, because of Matt's suggestion of the origin of error, written a
small C server that uses the same configuration and it works. Can someone
tell me what's going on?
The code is next (fully copied from my editor):
"#include
#include
#include
#include
#include
On 02/09/2016 03:27, Kyle Hamilton wrote:
On Thu, Sep 1, 2016 at 3:43 PM, Salz, Rich >wrote:
> The existence of the NSA agreement is a partial answer to the first
question,
> though it seems unclear if this license is recursively
On Thu, Sep 1, 2016 at 3:43 PM, Salz, Rich wrote:
> > The existence of the NSA agreement is a partial answer to the first
> question,
> > though it seems unclear if this license is recursively sublicensed
> through 3rd
> > parties or not.
>
> They knew they were licensing an
Dear OpenSSL team,
Given the recent patent lawsuit between RIM/CertiCom and Avaya
mentioning the ECC code in OpenSSL, what is (according to the
OpenSSL team) the patent status of the ECC code in OpenSSL?
Specifically:
- Was the OpenSSL ECC code provided under a still-valid patent
license from
And if you want to run it on OpenSSL-1.1, see the attached. ☺
--
Regards,
Uri Blumenthal
On 9/1/16, 6:18 , "openssl-users on behalf of mowiener"
wrote:
Many thanks Mounir, this is what I was looking for.
\
When compiling with FIPS, the compile terminated with a fatal error looking
for #include in the crypto/err/err_all.c code. The fips.h
header file lives in ../ssl/fips-2.0/include.openssl/fips.h.
Am I missing something here?
--
openssl-users mailing list
To unsubscribe:
12 matches
Mail list logo