Re: Linux linking issues moving from 1.0.2t to 1.1.1c

2019-10-08 Thread Richard Levitte
On Tue, 08 Oct 2019 18:53:37 +0200, Dan Heinz wrote: > > Another question is why I now need to link pthreads when I did not > in the 1.0.2 version? I've added no-threads to the configuration, > but I'm curious why I didn't need to previously link it. And I'd > prefer not to change too many

Re: debian openssh issue with openssl 1.1.1d

2019-10-08 Thread Viktor Dukhovni
> On Oct 8, 2019, at 6:27 AM, Benjamin Kaduk via openssl-users > wrote: > > The RNG uses sysV shm to convey to other processes that /dev/[u]random has > been > properly seeded, under some configurations/kernel versions. This apprently affects some sandboxed configurations:

RE: Linux linking issues moving from 1.0.2t to 1.1.1c

2019-10-08 Thread Dan Heinz
> > > >The no-dso is silently not valid in 1.1.1c. That option didn't work > > > >right, so it was unusable in practice anyway. However, someone recently > > > >fixed that up, unfortunately after the last 1.1.1 release. > > > >The specific patch may be possible to find on github (unless that

Re: Blake2b with key

2019-10-08 Thread Blumenthal, Uri - 0553 - MITLL
> > Is keyed blake2b supported in openssl-dgst (latest OpenSSL release)? > No, sorry. It has been added for upcoming OpenSSL 3.0, though. Doesn't look like it's there: $ openssl3 version OpenSSL 3.0.0-dev xx XXX (Library: OpenSSL 3.0.0-dev xx XXX ) $ echo -n "hello" |

Re: Blake2b with key

2019-10-08 Thread Blumenthal, Uri - 0553 - MITLL
Answered my own questions: $ openssl3 list -mac-algorithms Provided MACs: BLAKE2bMAC @ default BLAKE2sMAC @ default CMAC @ default GMAC @ default HMAC @ default KMAC128 @ default KMAC256 @ default Poly1305 @ default SipHash @ default $ $ echo -n "hello" | openssl3 mac -macopt

Re: Blake2b with key

2019-10-08 Thread Richard Levitte
On Tue, 08 Oct 2019 15:44:23 +0200, van Hemel, Wouter J M wrote: > > Hello, > > I'm trying to create a blake2b512 digest with a key. I've made an attempt to > follow the source code and I'm assuming the algorithm's name for blake2b MAC > is blake2bmac, though I have tried different values. I

Re: Linux linking issues moving from 1.0.2t to 1.1.1c

2019-10-08 Thread Richard Levitte
On Tue, 08 Oct 2019 14:59:23 +0200, Richard Levitte wrote: > > On Mon, 07 Oct 2019 21:55:50 +0200, > Dan Heinz wrote: > > > > >The no-dso is silently not valid in 1.1.1c. That option didn't work > > >right, so it was unusable in practice anyway. However, someone recently > > >fixed that up,

Blake2b with key

2019-10-08 Thread van Hemel, Wouter J M
Hello, I'm trying to create a blake2b512 digest with a key. I've made an attempt to follow the source code and I'm assuming the algorithm's name for blake2b MAC is blake2bmac, though I have tried different values. I don't seem to be able to create a valid checksum: $ openssl version; echo -n

Re: Linux linking issues moving from 1.0.2t to 1.1.1c

2019-10-08 Thread Richard Levitte
On Mon, 07 Oct 2019 21:55:50 +0200, Dan Heinz wrote: > > >The no-dso is silently not valid in 1.1.1c. That option didn't work right, > >so it was unusable in practice anyway. However, someone recently fixed that > >up, unfortunately after the last 1.1.1 release. > >The specific patch may be

Re: debian openssh issue with openssl 1.1.1d

2019-10-08 Thread Benjamin Kaduk via openssl-users
On Tue, Oct 08, 2019 at 05:23:56AM -0400, Michael Richardson wrote: > Salvatore Bonaccorso wrote: > > > - > > Debian Security Advisory DSA-4539-2 > secur...@debian.org > >

debian openssh issue with openssl 1.1.1d

2019-10-08 Thread Michael Richardson
Salvatore Bonaccorso wrote: > - > Debian Security Advisory DSA-4539-2 secur...@debian.org > https://www.debian.org/security/ Salvatore Bonaccorso > October 07, 2019

Re: OPENSSL_config vs OPENSSL_init_crypto

2019-10-08 Thread Matt Caswell
On 08/10/2019 00:20, Samuel Williams wrote: > Hello, > > I am trying to understand what is the correct initialization process for > Ruby's > SSL module. It's not my area so any input would be most welcome. > > https://github.com/ruby/openssl/pull/267 Reading that PR it seems your objective