Re: [openssl-users] s_server -www -tls1_3: Firefox/Chrome not working

2018-10-22 Thread Juan Isoza
I suppose Facebook reports 50% because their mobile apps uses their SSL library Fizz with Tls 1.3 https://thehackernews.com/2018/08/fizz-tls-ssl-library.html I'm curious seeing your telemetry info now. Chrome 70 was released last week, and FireFox 63 today, with TLS 1.3 support regards Le mer.

[openssl-users] How to compile 1.1.1 under Windows

2018-10-22 Thread Chris Clark
quot; -D"_WINSOCK_DEPRECATED_NO_WARNINGS" -D"OPENSSL_USE_APPLINK" -D"NDEBUG" /Zs /showIncludes "crypto\sm2\sm2_sign.c" 2>&1 > crypto\sm2\sm2_sign.d NMAKE : fatal error U1077: 'cl' : return code '0x2' Stop. NMAKE : fatal error U1077:

Re: [openssl-users] What to do with deprecation errors

2018-10-22 Thread pgndev
The "which package depends on which openssl ver" issue's been around a long time. FWIW, in general, I *never* touch openssl libs/headers in the default distro path, /usr. Just leave that alone -- too many distro packages (still) make (invalid) assumptions about that being the only/preferred openss

Re: [openssl-users] What to do with deprecation errors

2018-10-22 Thread Richard Levitte
If the compiler found opensslconf.h in /usr/include/x86_64-linux-gnu/openssl/, that usually means you have an distribution openssl package installed, one that other programs are relying on. Depending on the version of that package, you may have screwed things up or not. If you're lucky, things wi

Re: [openssl-users] What to do with deprecation errors

2018-10-22 Thread Jakob Bohm via openssl-users
Ah, I guess it wanted you to also compile OpenSSL for i386 and putting that (different!) opensslconf.h in the i386-specific directory. That also means you should have moved opensslconf.h to the subdir, not copied it. On 22/10/2018 20:42, Skip Carter wrote: Found the problem! Thanks to Selva for

Re: [openssl-users] What to do with deprecation errors

2018-10-22 Thread Skip Carter
Found the problem! Thanks to Selva for pointing the way. The compiler was looking for opensslconf.h (and only this file, not any other header files) at /usr/include/x86_64-linux- gnu/openssl/opensslconf.h when I copied /usr/include/openssl/opensslconf.h to that location, everything worked. The

Re: [openssl-users] What to do with deprecation errors

2018-10-22 Thread Skip Carter
On Mon, 2018-10-22 at 17:52 +, Salz, Rich via openssl-users wrote: > >    Yes the macro is there, its just not being expanded by the pre- > > compiler. >    > That makes no sense. I am stumped, FYI here is the the relevant output of the precompiler (cpp) # 261 "/usr/include/openssl/ec.h

Re: [openssl-users] What to do with deprecation errors

2018-10-22 Thread Richard Levitte
That's very odd. Are you *sure* the one you're looking at is the one actually included? Cheers, Richard In message <1540230631.4886.20.ca...@taygeta.com> on Mon, 22 Oct 2018 10:50:31 -0700, Skip Carter said: > Yes the macro is there, its just not being expanded by the pre- > compiler. > > >

Re: [openssl-users] What to do with deprecation errors

2018-10-22 Thread Selva Nair
On Mon, Oct 22, 2018 at 1:51 PM Skip Carter wrote: > > Yes the macro is there, its just not being expanded by the pre- > compiler. All these tests say the same thing that you are picking up a wrong (old) header. So do: gcc -E your-program.c | grep opensslconf.h Then check whether the one it pi

Re: [openssl-users] What to do with deprecation errors

2018-10-22 Thread Viktor Dukhovni
You're surely looking in the wrong header file. The compiler is using a different one in which the macro is NOT defined. > On Oct 22, 2018, at 1:50 PM, Skip Carter wrote: > > Yes the macro is there, its just not being expanded by the pre- > compiler. > > > On Mon, 2018-10-22 at 08:55 +0100, M

Re: [openssl-users] What to do with deprecation errors

2018-10-22 Thread Salz, Rich via openssl-users
>Yes the macro is there, its just not being expanded by the pre- compiler. That makes no sense. Please look at your compiler manpages and figure out how to turn on verbose compiler output. Something is strange in your environment. -- openssl-users mailing list To unsubscribe: ht

Re: [openssl-users] What to do with deprecation errors

2018-10-22 Thread Skip Carter
Yes the macro is there, its just not being expanded by the pre- compiler. On Mon, 2018-10-22 at 08:55 +0100, Matt Caswell wrote: > > On 21/10/2018 20:01, Skip Carter wrote: > > Does your opensslconf.h have the DEPRECATEDIN_1_2_0 macro defined in > it? > > Matt -- Skip Carter Taygeta Scientifi

Re: [openssl-users] Reg issue in alert message

2018-10-22 Thread Matt Caswell
On 22/10/2018 14:56, ramakrushna mishra wrote: > Hi, > > I am facing an issue after openssl upgrade to 1.1.1.  > I have a odbc client with maximum version support up to TLSv1.2 and  my > database is running with TLSv1.2,TLsv1.3.  > > The handhake is failing and I am getting following contents o

[openssl-users] Reg issue in alert message

2018-10-22 Thread ramakrushna mishra
Hi, I am facing an issue after openssl upgrade to 1.1.1. I have a odbc client with maximum version support up to TLSv1.2 and my database is running with TLSv1.2,TLsv1.3. The handhake is failing and I am getting following contents on my BIO dump. "15 03 03 00 02 02 56" . If i have understood corr

Re: [openssl-users] To disable CBC ciphers

2018-10-22 Thread Jakob Bohm via openssl-users
On 20/10/2018 15:59, Kaushal Shriyan wrote: On Wed, Oct 17, 2018 at 7:00 PM murugesh pitchaiah mailto:murugesh.pitcha...@gmail.com>> wrote: Hi, You may list down what ciphers configured : "openssl ciphers" Choose CBC ciphers and add them to the list of 'ssl_ciphers' with "!"

Re: [openssl-users] What to do with deprecation errors

2018-10-22 Thread Matt Caswell
On 21/10/2018 20:01, Skip Carter wrote: > Thats what I originally thought. > > I experimented with manually invoking the pre-compiler (cpp) and this > is what I get: > > > DEPRECATEDIN_1_2_0(int EC_GROUP_get_curve_GF2m(const EC_GROUP *group, >