[openssl-users] Changing the encoding in openssl

Hi champions, I would like to use the openssl for encrypting the data and would like to get the encrypted data in "hex" format rather than UTF-8 format. Lets I have a bytes "90909090909090909090909090909090" i.e. of 16 bytes in hex(each char takes 1 nibble when you load into memory). After encrypt

Re: [openssl-users] follow-up to: ChaCha20/Poly1305 in OpenSSL?

pebkac. clean re-DL of Openssl 1.0.2f sources fixes that ; patch applies cleanly. -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] follow-up to: ChaCha20/Poly1305 in OpenSSL?

On Wed, Feb 17, 2016, at 06:05 PM, Salz, Rich wrote: > > > (1) 1.0.2f + cloudflare patch > > (2) 1.1.0-alpha3 > > Did CF update their patch to the official version and codepoints? Cool. > Apparently. But 1st try has one glitch ... patch -p1 < openssl__chacha20_poly1305_draft_and_rfc_ossl10

Re: [openssl-users] follow-up to: ChaCha20/Poly1305 in OpenSSL?

> (1) 1.0.2f + cloudflare patch > (2) 1.1.0-alpha3 Did CF update their patch to the official version and codepoints? Cool. -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] follow-up to: ChaCha20/Poly1305 in OpenSSL?

On Wed, Feb 17, 2016, at 06:00 PM, Salz, Rich wrote: > > What's current plan status for these ciphers? > > > > Not until 1.1.0 release? Or earlier? > > Yup, 1.1. It's a new feature so it doesn't go into current releases which > only get fixes. Thanks. > And the code that's in master, which

Re: [openssl-users] follow-up to: ChaCha20/Poly1305 in OpenSSL?

> What's current plan status for these ciphers? > > Not until 1.1.0 release? Or earlier? Yup, 1.1. It's a new feature so it doesn't go into current releases which only get fixes. And the code that's in master, which just released alpha-3, rocks. :) -- openssl-users mailing list To unsubscr

[openssl-users] follow-up to: ChaCha20/Poly1305 in OpenSSL?

I'm looking for Openssl's Chacha20/Poly1305 cipher support, supported client-side in Chrome/Chromium-dev, and server-side in Nginx. Last I was able to find on list [openssl-users] ChaCha20/Poly1305 in OpenSSL? Fri Mar 27 05:05:59 UTC 2015 https://mta.openssl.org/pipermail

[openssl-users] follow-up to: ChaCha20/Poly1305 in OpenSSL?

I'm looking for Openssl's Chacha20/Poly1305 cipher support, supported client-side in Chrome/Chromium-dev, and server-side in Nginx. Last I was able to find on list [openssl-users] ChaCha20/Poly1305 in OpenSSL? Fri Mar 27 05:05:59 UTC 2015 https://mta.openssl.org/pipermail

Re: [openssl-users] Statically link FIPS OpenSSL to shared library application

My problem was solved by adding -Wl,-Bsymbolic to the list of compiler flags. I found this from an old post on this mailing list. It's still not clear why this flag is needed though. -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] Statically link FIPS OpenSSL to shared library application

On Wed, Feb 17, 2016, Gustavo Tabares wrote: > Hello, > > I???m trying to statically link OpenSSL to my C++ shared library application > on Linux. I???ve followed the instructions outlined in the Fipsld and C++ > Wiki page and everything builds fine. However I???m getting a fingerprint > mismatch

Re: [openssl-users] Statically link FIPS OpenSSL to shared library application

Are you supplying a base address for the shared library when linking? I ran into this same problem but for Win32 .dll, but I'm not sure if there is the same requirement for Linux so's. The problem was without supplying a base address, the HMAC signature could not be found and the power on self test

[openssl-users] Intermittent SSL_shutdown error

Hi, I am trying to create a SSL connection (call it connection 2) inside another SSL connection (call it connection 1). Connection 2 is used to connect to a machine which is hidden behind the machine to which I connect using connection 1. Once Connection 2 is established (i.e. SSL handshake finish

[openssl-users] Possible bug - SSL_ERROR_RX_UNEXPECTED_CHANGE_CIPHER error in FireFox 44.0

Hello, I'm hoping you could provide some assistance in diagnosing/investigating an issue my users are experiencing with FireFox. Our CDN is using OpenSSL 1.0.1j-1.4.0.420. In addition to the below, I did try contacting Dr. Henson on this topic (his name was referenced in some of the old online

[openssl-users] Statically link FIPS OpenSSL to shared library application

Hello, I’m trying to statically link OpenSSL to my C++ shared library application on Linux. I’ve followed the instructions outlined in the Fipsld and C++ Wiki page and everything builds fine. However I’m getting a fingerprint mismatch when calling FIPS_mode_set. If I change my shared library to an

Re: [openssl-users] ciphers

If all you want is TLS 1.2, then this line is enough: > >> SSLProtocol -All +TLSv1.2 > >> SSLCompression off > >> SSLInsecureRenegotiation off -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] [openssl-dev] OpenSSL version 1.1.0 pre release 3 published

Dear Rich, > Just to emphasize one important point: Our next release is planned to be > Beta-1, in about a month. After that, no new API's or features will be > added to OpenSSL 1.1 > > If so, could you take a look at RT#4267? Thank you! -- SY, Dmitry Belyavsky -- openssl-users mailing list