[openssl-users] X25519 - why openssl shows server temp key as 253 bits?

Hi, When using openssl with X25519, why it shows the server temp key as 253 bits? Example: --- No client certificate CA names sent Peer signing digest: SHA256 Peer signature type: RSA Server Temp Key: X25519, 253 bits --- I thought Curve25519 is using 256 bit keys. Why 253 instead of 256?

Re: [openssl-users] OpenSSL version 1.1.0i make test fails - 80-test_cms.t

> On Sep 4, 2018, at 12:16 AM, James Brown via openssl-users > wrote: > > Running ‘make test’ for 1.1.0i fails with: > > Test Summary Report > --- > ../test/recipes/80-test_cms.t(Wstat: 256 Tests: 4 Failed: 1) > Failed test: 4 > Non-zero exit status: 1 >

[openssl-users] OpenSSL version 1.1.0i make test fails - 80-test_cms.t

Running ‘make test’ for 1.1.0i fails with: Test Summary Report --- ../test/recipes/80-test_cms.t(Wstat: 256 Tests: 4 Failed: 1) Failed test: 4 Non-zero exit status: 1 Files=99, Tests=561, 83 wallclock secs ( 0.94 usr 0.23 sys + 49.59 cusr 22.30 csys = 73.06 CPU)

Re: [openssl-users] build.info

Using the linux env var LD_PRELOAD, maybe? ⁣Sent from BlueMail ​ On Sep 3, 2018, 15:05, at 15:05, "Thomás Inskip" wrote: >Does anyone know how I can specify that a specific shared library (in >this >case an engine) is dependent on a system-installed shared library (i.e. >not >built along with

[openssl-users] stunnel 5.49 released

Dear Users, I have released version 5.49 of stunnel. Version 5.49, 2018.09.03, urgency: MEDIUM * New features   - Performance optimizations.   - Logging of negotiated or resumed TLS session IDs (thx     to ANSSI - National Cybersecurity Agency of France).   - Merged Debian 10-enabled.patch and

[openssl-users] build.info

Does anyone know how I can specify that a specific shared library (in this case an engine) is dependent on a system-installed shared library (i.e. not built along with openssl)?. Basically the equivalent of LDFLAGS += -lsomelib -- openssl-users mailing list To unsubscribe:

Re: [openssl-users] Engines on Mac OS X

Ouch... Spelling Corrector doing is best. The text below should've been: "... spitting out a pile of error..." Oh well. Hard to admit, but sometimes automatic correctors are even more eloquent than me, and seem freeer in their choice of words too. ;-) Regards, Uri Sent from my iPhone > On

Re: [openssl-users] Engines on Mac OS X

If it builds a dummy engine - then shouldn't a dummy engine respond gracefully to requests with something like "sorry I can't do anything useful", instead of spitting outa puke of error messages in response to "openssl engine -t capi"? Regards, Uri Sent from my iPhone > On Sep 3, 2018, at

Re: [openssl-users] Engines on Mac OS X

In message <62b8aa9b-d6d2-4f33-94c5-7bfe11e46...@akamai.com> on Mon, 3 Sep 2018 13:56:41 +, "Salz, Rich" said: > > Gotcha. In that case why does it get built on Mac? I.e., why > > doesn’t the build process exclude it automatically? > > Beats me. It ends up being a zero-length object file,

Re: [openssl-users] Engines on Mac OS X

On 03/09/18 14:56, Salz, Rich via openssl-users wrote: > *>*Gotcha. In that case why does it get built on Mac? I.e., why doesn’t > the build process exclude it automatically? > >   > > Beats me.  It ends up being a zero-length object file, more or less.  > Perhaps Richard Levitte knows. It

Re: [openssl-users] Engines on Mac OS X

>Gotcha. In that case why does it get built on Mac? I.e., why doesn’t the build >process exclude it automatically? Beats me. It ends up being a zero-length object file, more or less. Perhaps Richard Levitte knows. -- openssl-users mailing list To unsubscribe:

[openssl-users] curl and wget not working with https sites after upgrade to ubuntu 18.04.1

Seems to be a openssl related issue. Anyone have any ideas as to what this is? Note that the url works in a browser. With wget: # wget -d https://deb.nodesource.com/setup_8.x DEBUG output created by Wget 1.19.4 on linux-gnu. Reading HSTS entries from /home/user/.wget-hsts URI