Re: [openssl-dev] Missing EVP_PKEY_meth_get_xxx methods?

Matt and Steve, Thank you! I indeed fancied creating a PR to add those: https://github.com/openssl/openssl/pull/4452 ;-) -- Regards, Uri Blumenthal On 10/2/17, 12:41, "openssl-dev on behalf of Dr. Stephen Henson" wrote: On

Re: [openssl-dev] Missing EVP_PKEY_meth_get_xxx methods?

On Mon, Oct 02, 2017, Matt Caswell wrote: > > > On 02/10/17 15:00, Blumenthal, Uri - 0553 - MITLL wrote: > > Moving to openssl-dev, because I think OpenSSL-1.0.2 needs a fix. > > > >   > > > > To be more specific, the following get methods are missing in 1.0.2: > > > >   > > > > -

Re: [openssl-dev] Missing EVP_PKEY_meth_get_xxx methods?

On 02/10/17 15:00, Blumenthal, Uri - 0553 - MITLL wrote: > Moving to openssl-dev, because I think OpenSSL-1.0.2 needs a fix. > >   > > To be more specific, the following get methods are missing in 1.0.2: > >   > > - EVP_PKEY_meth_get_sign(EVP_PKEY_METHOD *,  …) > > -

[openssl-dev] Missing EVP_PKEY_meth_get_xxx methods?

Moving to openssl-dev, because I think OpenSSL-1.0.2 needs a fix. To be more specific, the following get methods are missing in 1.0.2: - EVP_PKEY_meth_get_sign(EVP_PKEY_METHOD *,  …) - EVP_PKEY_meth_get_decrypt(EVP_PKEY_METHOD *,  …) - EVP_PKEY_meth_get_encrypt(EVP_PKEY_METHOD *,  …)

[openssl-dev] Patch for iOS compilation failure on Xcode 9 / iOS 11 SDK

"-fomit-frame-pointer" is no longer allowed for armv7 targets, so I removed it from the iphoneos-cross configure target. I noticed this on openssl-1.0.2l. --- Configure.orig 2017-05-25 05:54:38.0 -0700 +++ Configure 2017-09-29 12:09:45.0 -0700 @@ -652,7 +652,7 @@

Re: [openssl-dev] why TLSv1 need two tls1_enc to get decrypted data while TLSv1.1/TLSv1.2 need one in OpenSSL1.1.0f?

Hi, Matt First, sorry for the mistake I made. In fact, with openSSL1.0.2 as the server, tls1_enc will be called twice in TLSv1, so it's not a timing issue. And besides, we don't rely on SSL_read will definitely result in readable data being decrypted, I'm just saying the most general process, of

Re: [openssl-dev] why TLSv1 need two tls1_enc to get decrypted data while TLSv1.1/TLSv1.2 need one in OpenSSL1.1.0f?

Hi, Matt Thanks for your quickly response. And yes, with this option SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS in client side the result can be get from one decryption. But the problem is, sometimes we can't control client's behavior. Maybe the client is openssl s_client, or maybe it's a python

[openssl-dev] FIPS 186-4

Hi All, Any pointers of FIPS 186-4 compliant source code patch for openssl FIPS ? Any help appreciated. Thanks, Murugesh P. -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] Systemwide configurability of OpenSSL

Hello. Tomas Mraz wrote: |I would like to restart the discussion about possibilities of system- |wide configurability of OpenSSL and particularly libssl. | |Historically OpenSSL allowed only for configuration of the enabled |ciphersuites list if application called

Re: [openssl-dev] Bug in pkey_rsa_encrypt() and _decrypt()

> Working on pkcs11 engine, I discovered a bug in crypto/rsa/rsa_pmeth.c in pkey_rsa_encrypt() and pkey_rsa_decrypt(). > > They cause a crash when called with out==NULL. Normally it should not happen > but when an engine is called, and it cannot process the padding it reverts

Re: [openssl-dev] Bug in pkey_rsa_encrypt() and _decrypt()

On Tue, Sep 26, 2017, Blumenthal, Uri - 0553 - MITLL wrote: > Working on pkcs11 engine, I discovered a bug in crypto/rsa/rsa_pmeth.c in > pkey_rsa_encrypt() and pkey_rsa_decrypt(). > > They cause a crash when called with out==NULL. Normally it should not happen > ??? but when an engine is

Re: [openssl-dev] New crypto algorithms in openSSL engine

On 27/09/17 15:32, Byrne, Andrew wrote: > I’m working on testing some lattice based algorithms in openSSL for the > establishment of a TLS channel. I’ve investigated the potential for > developing an engine to support this as it would mean I don’t need to > touch the core openSSL code. However,

Re: [openssl-dev] why TLSv1 need two tls1_enc to get decrypted data while TLSv1.1/TLSv1.2 need one in OpenSSL1.1.0f?

On 27/09/17 15:44, Ma chunhui wrote: > Hi,  > > I met one problem when using OpenSSL1.1.0f with protocol TLSv1. > In brief, when using TLSv1,  after server side received encrypted data, > and after function tls1_enc finished, the decrypted data is not put in > result buffer, after another

[openssl-dev] Systemwide configurability of OpenSSL

I would like to restart the discussion about possibilities of system- wide configurability of OpenSSL and particularly libssl. Historically OpenSSL allowed only for configuration of the enabled ciphersuites list if application called appropriate API call. This is now enhanced with the SSL_CONF

[openssl-dev] New crypto algorithms in openSSL engine

Hi all, I'm working on testing some lattice based algorithms in openSSL for the establishment of a TLS channel. I've investigated the potential for developing an engine to support this as it would mean I don't need to touch the core openSSL code. However, I've two blind spots which I can't

[openssl-dev] why TLSv1 need two tls1_enc to get decrypted data while TLSv1.1/TLSv1.2 need one in OpenSSL1.1.0f?

Hi, I met one problem when using OpenSSL1.1.0f with protocol TLSv1. In brief, when using TLSv1, after server side received encrypted data, and after function tls1_enc finished, the decrypted data is not put in result buffer, after another tls1_enc, the decrypted data is put in result buffer.

Re: [openssl-dev] how to static compile ssl engine into openssl

In message <20170926203053.5hlfcbx273lko...@roeckx.be> on Tue, 26 Sep 2017 22:30:53 +0200, Kurt Roeckx said: kurt> On Tue, Sep 26, 2017 at 07:32:06AM +0200, Richard Levitte wrote: kurt> > kurt> > You mean to have nginx use the shared OpenSSL libraries, which also kurt> >

Re: [openssl-dev] how to static compile ssl engine into openssl

On Tue, Sep 26, 2017 at 07:32:06AM +0200, Richard Levitte wrote: > > You mean to have nginx use the shared OpenSSL libraries, which also > enables dynamic engines? Yes, that's the usual way to go about these > things. Do we support dynamic engines with a static build? Kurt -- openssl-dev

[openssl-dev] Bug in pkey_rsa_encrypt() and _decrypt()

Working on pkcs11 engine, I discovered a bug in crypto/rsa/rsa_pmeth.c in pkey_rsa_encrypt() and pkey_rsa_decrypt(). They cause a crash when called with out==NULL. Normally it should not happen – but when an engine is called, and it cannot process the padding – it reverts to the original

Re: [openssl-dev] how to static compile ssl engine into openssl

On 26/09/2017, Levitte, Richard via openssl-dev wrote: > > chengwenping1> I?m working on accelerating ssl traffic with Intel QAT > chengwenping1> card, now openssl 1.1.0f is integrated into Nginx, so I > chengwenping1> need to static compile Intel QAT engine into openssl, and > chengwenping1> I

[openssl-dev] 答复: how to static compile ssl engine into openssl

There is some more info. https://github.com/01org/QAT_Engine/issues/9 -邮件原件- 发件人: 程文平 发送时间: 2017年9月26日 17:43 收件人: openssl-dev@openssl.org 主题: 答复: [openssl-dev] how to static compile ssl engine into openssl Hi Richard, Thanks for your response. From your meaning, the QAT engine

[openssl-dev] 答复: how to static compile ssl engine into openssl

Hi Richard, Thanks for your response. From your meaning, the QAT engine codes is not applicable for static compile into openssl. Yes, I should keep to run nginx using shared OpenSSL libraries with dynamic QAT engines installed, until QAT engine static compiling is support.

Re: [openssl-dev] how to static compile ssl engine into openssl

In message <31F771DF13463A429610AEEBF6AFAE820182EBC4@mbx14.360buyAD.local> on Mon, 25 Sep 2017 10:16:28 +, 程文平 said: chengwenping1> I’m working on accelerating ssl traffic with Intel QAT chengwenping1> card, now openssl 1.1.0f is integrated into Nginx, so I

[openssl-dev] how to static compile ssl engine into openssl

Hi all, I’m working on accelerating ssl traffic with Intel QAT card, now openssl 1.1.0f is integrated into Nginx, so I need to static compile Intel QAT engine into openssl, and I do not find some useful info about it from Internet, although openssl-1.1.0f/engines/ build.info, it is

Re: [openssl-dev] Creating requests and certificates with Subject Alternative Names

> I'm creating X509 certificate requests and certificates in code, > trying to add X509v3 Subject Alternative Name, with 1.1.0f. > > But if I add a list of four domains, ie: > The certificate seems to ignore some and repeat others: To answer my own question, I was using ASN1_STRING_set0

[openssl-dev] Openssl FIPS ecp 2.0.16: KDF test for TLS and SSH : Segmentation fault

Hi All, I am working on doing the KDF testing. Done with the HMAC and SHA. But when it comes to do the same for TLS and SSH, evidenced that openssl does not support it. As suggested by old threads, added the patch from Cisco: https://github.com/openssl/openssl/pull/368/files Did build. Now i

Re: [openssl-dev] libcrypto.pc needs to list libpthread as a dependency

In message <59bebf25.5040...@roumenpetrov.info> on Sun, 17 Sep 2017 21:29:57 +0300, Roumen Petrov said: openssl> Hi Howard, openssl> openssl> Howard Chu wrote: openssl> > Roumen Petrov wrote: openssl> >> Howard Chu via openssl-dev wrote: openssl> >>> In OpenSSL 1.1

Re: [openssl-dev] Bug: digest parameter is rejected

See crypto/rsa/rsa_pmeth.c pkey_rsa_ctrl_str for the options. There is also rsa_oaep_label Thank you!! That saved the day: . . . . . Where can I see the complete list of the options that “-pkeyopt” supports now? I missed the crypto/rsa/rsa_pmeth.c

Re: [openssl-dev] Bug: digest parameter is rejected

On 09/18/2017 09:32 AM, Blumenthal, Uri - 0553 - MITLL wrote: > > RSA-OAEP supports different hash functions and MGF. SHA-1 is the default. > >   > > OpenSSL implementation of OAEP wrongly refuses to set the hash > algorithm, preventing one from using SHA-2 family: > > You'll probably need to

[openssl-dev] Bug: digest parameter is rejected

RSA-OAEP supports different hash functions and MGF. SHA-1 is the default. OpenSSL implementation of OAEP wrongly refuses to set the hash algorithm, preventing one from using SHA-2 family: $ openssl version OpenSSL 1.0.2l  25 May 2017 $ openssl pkeyutl -encrypt -in t1264.dat -out

Re: [openssl-dev] TLS 1.3 client hello issue

Thanks for responding. Yes, I have done the steps mentioned above. Here are my settings: int min_version = TLS1_3_VERSION, max_version = TLS1_3_VERSION; meth = isClient ? tlsv1_3_client_method() : tlsv1_3_server_method(); //meth = isClient ? TLS_client_method() :

Re: [openssl-dev] TLS 1.3 client hello issue

On 09/18/2017 01:07 AM, Mahesh Bhoothapuri wrote: > > Hi, > > I am sending a Tls 1.3 client hello, and am seeing an issue with > > ossl_statem_client_write_transition in statem_clnt.c. > > >     /* > * Note that immediately before/after a ClientHello we don't know what > * version we are

[openssl-dev] TLS 1.3 client hello issue

Hi, I am sending a Tls 1.3 client hello, and am seeing an issue with ossl_statem_client_write_transition in statem_clnt.c. /* * Note that immediately before/after a ClientHello we don't know what * version we are going to negotiate yet, so we don't take this branch until *

Re: [openssl-dev] libcrypto.pc needs to list libpthread as a dependency

On Sun, Sep 17, 2017 at 08:04:10AM +0100, Matt Caswell wrote: > On Sat, 16 Sep 2017 22:26:10 +0100 > Howard Chu via openssl-dev wrote: > > > In OpenSSL 1.1 on Linux (at least) libcrypto now has a dependency on > > libpthread but this is not reflected in the pkgconfig

Re: [openssl-dev] libcrypto.pc needs to list libpthread as a dependency

Roumen Petrov wrote: Howard Chu via openssl-dev wrote: In OpenSSL 1.1 on Linux (at least) libcrypto now has a dependency on libpthread but this is not reflected in the pkgconfig file. As a result, tools like CMake fail to detect libcrypto properly when linking against the static library.

Re: [openssl-dev] libcrypto.pc needs to list libpthread as a dependency

Matt Caswell skrev: (17 september 2017 15:04:10 GMT+08:00) >On Sat, 16 Sep 2017 22:26:10 +0100 >Howard Chu via openssl-dev wrote: > >> In OpenSSL 1.1 on Linux (at least) libcrypto now has a dependency on >> libpthread but this is not reflected in the

Re: [openssl-dev] libcrypto.pc needs to list libpthread as a dependency

On Sat, 16 Sep 2017 22:26:10 +0100 Howard Chu via openssl-dev wrote: > In OpenSSL 1.1 on Linux (at least) libcrypto now has a dependency on > libpthread but this is not reflected in the pkgconfig file. As a result, > tools > like CMake fail to detect libcrypto

[openssl-dev] libcrypto.pc needs to list libpthread as a dependency

In OpenSSL 1.1 on Linux (at least) libcrypto now has a dependency on libpthread but this is not reflected in the pkgconfig file. As a result, tools like CMake fail to detect libcrypto properly when linking against the static library. libpthread should be added to the Libs.private line of the

Re: [openssl-dev] OPenssl 1.1.0 and FIPS

> FIPS is not supported for 1.1.0 > >jUST A SMALL FIX WILL DO. No. All of the FIPS supporting code has been pulled out of 1.1.0 Even if you get it to compile, it will fail at link or runtime because of missing functions. -- openssl-dev mailing list To unsubscribe:

Re: [openssl-dev] OPenssl 1.1.0 and FIPS

The Doctor skrev: (16 september 2017 15:26:16 CEST) >On Sat, Sep 16, 2017 at 12:56:08PM +, Salz, Rich via openssl-dev >wrote: >> >> Tryong to compile Fips into OPEnssl-1.1.0 and I run into >> >> FIPS is not supported for 1.1.0 >> > >jUST A SMALL FIX

Re: [openssl-dev] OPenssl 1.1.0 and FIPS

On Sat, Sep 16, 2017 at 12:56:08PM +, Salz, Rich via openssl-dev wrote: > > Tryong to compile Fips into OPEnssl-1.1.0 and I run into > > FIPS is not supported for 1.1.0 > jUST A SMALL FIX WILL DO. > -- > openssl-dev mailing list > To unsubscribe:

Re: [openssl-dev] OPenssl 1.1.0 and FIPS

Tryong to compile Fips into OPEnssl-1.1.0 and I run into FIPS is not supported for 1.1.0 -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

[openssl-dev] OPenssl 1.1.0 and FIPS

I thought it was just me. Tryong to compile Fips into OPEnssl-1.1.0 and I run into cc: warning: argument unused during compilation: '-rdynamic' [-Wunused-command-line-argument] crypto/err/err_all.c:47:69: error: invalid operands to binary expression ('void' and 'int')

Re: [openssl-dev] 20170914 snapshots

We did some system upgrades and they were down during the update time. As I’ve said before, please wait for at least a second day before writing about the snapshots. On 9/14/17, 8:09 AM, "The Doctor" wrote: They are missing in action! -- openssl-dev mailing

[openssl-dev] 20170914 snapshots

They are missing in action! -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism Talk Sense to a fool and

Re: [openssl-dev] SSL certificate problem: unable to get local issuer certificate

Hi Arthur, did you read the curl docs, especially on TLS? -> https://ec.haxx.se/usingcurl-tls.html Have you run curl from a command line in verbose mode on all machines? What are the results? Can you give the Yahoo URL for others to check? Regards, Ted Marynicz On 13 September 2017 at

[openssl-dev] SSL certificate problem: unable to get local issuer certificate

Dear sir or madam, I’m trying to use quantmod package in R to get financial data from Yahoo. It works perfectly on my personal laptops (Mac and Win). But I cannot make it work on my working computer (Win7). Here's the error code: Error in curl::curl_download(cu, tmp, handle = h) : SSL

Re: [openssl-dev] id-kp-OCSPSigning extended key usage

Bonjour, SHALL is not equivalent to a SHOULD, but to a MUST. See RFC2119. Cordialement, Erwann Abalea Le 12 sept. 2017 à 02:46, Winter Mute > a écrit : Hello, The RFC states that: OCSP signing

Re: [openssl-dev] id-kp-OCSPSigning extended key usage

➢ Thanks for the clarification. Per the spec, then, a certificate designated to sign OCSP responses is required to have the ocsp-sign bit in the key usage extensions set. ➢ How does openssl handle cases where this requirement is violated? Look at check_delegated() in ocsp/ocsp_vfy.c It returns

Re: [openssl-dev] id-kp-OCSPSigning extended key usage

Hi, Thanks for the clarification. Per the spec, then, a certificate designated to sign OCSP responses is required to have the ocsp-sign bit in the key usage extensions set. How does openssl handle cases where this requirement is violated? On Sep 12, 2017 3:27 PM, "Mischa Salle"

Re: [openssl-dev] id-kp-OCSPSigning extended key usage

Hi, On Tue, Sep 12, 2017 at 2:46 AM, Winter Mute wrote: > Hello, > The RFC states that: > >> OCSP signing delegation SHALL be designated by the inclusion of >> id-kp-OCSPSigning in an extended key usage certificate

[openssl-dev] id-kp-OCSPSigning extended key usage

Hello, The RFC states that: > OCSP signing delegation SHALL be designated by the inclusion of > id-kp-OCSPSigning in an extended key usage certificate extension > included in the OCSP response signer's certificate. The use of "SHALL" rather

Re: [openssl-dev] X509_cmp_time (possible) bug

Correct, But if one want’s strcmp()’s behavior (i.e. 0 is equality), ASN1_TIME_cmp_time_t() will work (and was written because X509_cmp_time() couldn’t be changed without breaking other things). -- -Todd Short // tsh...@akamai.com // "One if by land, two if by sea,

Re: [openssl-dev] X509_cmp_time (possible) bug

On Mon 2017-09-11 14:16:11 +, Short, Todd via openssl-dev wrote: > Yes, it’s annoying, but it’s historic. I looked into changing this at one > point. I think Dimitry's point was that the documentation doesn't match the implementation because of the flexibility of strcmp's defined return

Re: [openssl-dev] X509_cmp_time (possible) bug

Yes, it’s annoying, but it’s historic. I looked into changing this at one point. I recommend using ASN1_TIME_cmp_time_t() (from the master branch) instead, for the results you are expecting. -- -Todd Short // tsh...@akamai.com // "One if by land, two if by sea, three if

Re: [openssl-dev] Openssl and MAC KeyChain tool Integration

My understanding is there currently is no OpenSSL engine for the MacOSX chain services. It would be nice to have and I really wish I had time to collaborate on such a project, using Stephen Henson's CAPI work as a template. Currently I would suggest following the same model as OpenSSL for other

[openssl-dev] X509_cmp_time (possible) bug

Hello, The X509_cmp_time function is documented as returning -1 or 1 on success and 0 on error. In fact it returns result of strcmp: int X509_cmp_time(const ASN1_TIME *ctm, time_t *cmp_time) { ... i = strcmp(buff1, buff2); if (i == 0) /* wait a second then return younger

Re: [openssl-dev] QUIC

On 09/06/2017 05:24 PM, Matt Caswell wrote: > Issue 4283 (https://github.com/openssl/openssl/issues/4283) has caused > me to take a close look at QUIC. This seems to have been getting a *lot* > of attention just recently. See the IDs below for details: Yes, it's generated a lot of excitement and

[openssl-dev] QUIC

Issue 4283 (https://github.com/openssl/openssl/issues/4283) has caused me to take a close look at QUIC. This seems to have been getting a *lot* of attention just recently. See the IDs below for details: https://tools.ietf.org/html/draft-ietf-quic-transport-05

[openssl-dev] Introduce a TLS application library - a proposal on the overall OpenSSL code structure

Back on 13 May 2016 I had proposed by email to a couple of people including Rich Salz a third library level (on top of crypto and ssl) with more high-level, application-oriented code. His response was: > That is a really interesting idea. Please bring this up on openssl-dev > mailing list. Then

Re: [openssl-dev] How to use BIO_do_connect(), blocking and non-blocking with timeout, coping with errors

/[ Further below I quote my first two messages including my original questions and tentative code,// // since Cc'ing to openssl-users did not work when I tried first. In this way I hope to get further, // // more detailed responses by people with specific experience on the issues I mentioned,// // 

Re: [openssl-dev] 1.1.1 master consistently fails (was Re: openssl 1-1-0-stable fails)

Fix confirmed, thank you! Regards, Uri Sent from my iPhone > On Sep 4, 2017, at 10:25, Matt Caswell wrote: > > > >> On 04/09/17 08:59, Matt Caswell wrote: >> >> >>> On 03/09/17 22:18, Blumenthal, Uri - 0553 - MITLL wrote: >>> MacOS 10.12.6, Xcode-8.3.3. Current Github

Re: [openssl-dev] 1.1.1 master consistently fails (was Re: openssl 1-1-0-stable fails)

On 03/09/17 22:18, Blumenthal, Uri - 0553 - MITLL wrote: > MacOS 10.12.6, Xcode-8.3.3. Current Github master: > > Test Summary Report > --- > ../test/recipes/70-test_clienthello.t(Wstat: 256 Tests: 1 > Failed: 1) > Failed test: 1 > Non-zero exit status: 1 >

Re: [openssl-dev] TLS 1.3 non compliance with current draft

On 01/09/17 18:05, Hubert Kario wrote: > When openssl sends a second Client Hello message, it modifies it quite > extensively, not only client_random is changed but also advertised cipher > suites. > > see https://github.com/openssl/openssl/issues/4292 > > That makes it non-compliant with

Re: [openssl-dev] 1.1.1 master consistently fails (was Re: openssl 1-1-0-stable fails)

Ø Config & build script (feel free to suggest improvements, BTW): Perhaps don’t cut/paste green-on-black color? Plaintext is probably sufficient. -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

I like this PR. Thank you! > On Sep 3, 2017, at 17:53, Dr. Matthias St. Pierre > wrote: > >> >> The 'RAND_add()/RAND_bytes()' pattern is broken >> === >> >> In OpenSSL, the classical way for the RNG consumer to add his

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

> > The 'RAND_add()/RAND_bytes()' pattern is broken > === > > In OpenSSL, the classical way for the RNG consumer to add his own randomness > is to call 'RAND_add()' before > calling 'RAND_bytes()'. If the new 'RAND_OpenSSL()' method (the >

[openssl-dev] 1.1.1 master consistently fails (was Re: openssl 1-1-0-stable fails)

MacOS 10.12.6, Xcode-8.3.3. Current Github master: Test Summary Report --- ../test/recipes/70-test_clienthello.t(Wstat: 256 Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 1 Files=136, Tests=1266, 461 wallclock secs ( 2.58 usr 0.48 sys + 221.36 cusr

Re: [openssl-dev] Fwd: openssl 1-1-0-stable fails

All my builds include "make distclean" at the start of the process. However when I repeated that cleanup and re-run the build, 1_1_0-stable error disappeared. A fluke?! Regards, Uri Sent from my iPhone > On Sep 1, 2017, at 21:10, Blumenthal, Uri - 0553 - MITLL > wrote: > >

Re: [openssl-dev] Fwd: openssl 1-1-0-stable fails

On Sep 1, 2017, at 18:48, Matt Caswell wrote: >>> *Subject:* *openssl 1-1-0-stable fails* >>> >>> OpenSSL_1_1_0-stable current Github >>> >>> Test Summary Report >>> --- >>> ../test/recipes/80-test_cms.t(Wstat: 256 Tests: 4 Failed: 1) >>> Failed

Re: [openssl-dev] Fwd: openssl 1-1-0-stable fails

On 01/09/17 23:42, Blumenthal, Uri - 0553 - MITLL wrote: > > > Begin forwarded > >> *Subject:* *openssl 1-1-0-stable fails* >> >> OpenSSL_1_1_0-stable current Github >> >> Test Summary Report >> --- >> ../test/recipes/80-test_cms.t(Wstat: 256 Tests: 4 Failed: 1)

[openssl-dev] Fwd: openssl 1-1-0-stable fails

Begin forwarded > Subject: openssl 1-1-0-stable fails > > OpenSSL_1_1_0-stable current Github > > Test Summary Report > --- > ../test/recipes/80-test_cms.t(Wstat: 256 Tests: 4 Failed: 1) > Failed test: 4 > Non-zero exit status: 1 > Files=95, Tests=561, 165

Re: [openssl-dev] How to use BIO_do_connect(), blocking and non-blocking with timeout, coping with errors

FWIW, there’s a ‘libtls’ library from the libre folks that might be worth looking at. If you come up with useful snippets we can start by posting them to the wiki, for example -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

[openssl-dev] TLS 1.3 non compliance with current draft

When openssl sends a second Client Hello message, it modifies it quite extensively, not only client_random is changed but also advertised cipher suites. see https://github.com/openssl/openssl/issues/4292 That makes it non-compliant with the current draft (-21): When a client first connects

Re: [openssl-dev] how to compile out selected ciphers

On Thursday, 31 August 2017 11:13:13 CEST Richard Levitte wrote: > In message >

Re: [openssl-dev] [openssl-users] how to compile out selected ciphers

What version of openssl are you building? -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] how to compile out selected ciphers

In message

[openssl-dev] how to compile out selected ciphers

Hi All, I am trying to build openssl. As part of that I want to remove some ciphers like md4, rc5 etc. I tried ./config no-md5, no-rc5 and ./Configure no-md5, no-rc5. In both the case MD4 and RC5 directories are still getting compiled. Please can you let me know what could be going wrong.

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

To access a PKCS#11 randomness source, it would be necessary to have an engine that implemented whatever new RNG API is defined which in turn talks to the P11 device. Possibly not ideal but workable. As for the entropy argument to RAND_add et al, the callee will use it in a manner suitable to

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

> -Ursprüngliche Nachricht- > Von: openssl-dev [mailto:openssl-dev-boun...@openssl.org] Im Auftrag von > Blumenthal, Uri - 0553 - MITLL > Gesendet: Mittwoch, 30. August 2017 17:23 > An: openssl-dev@openssl.org > Betreff: Re: [openssl-dev] Plea for a new public OpenSSL RNG API > > ... > >

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

>> I would do exactly the opposite. “Normal” entropy is fetched from the default sources (/dev/urandom). But >> when a sensitive (aka long-term) keys are generated, a (portable :) hardware RNG is plugged in and used with >> RAND_add() equivalent. Reason – in my setup reliable trusted

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

> > We have a similar situation, on a small hardware device with little > own entropy > > but with a smartcard reader. > > Yes, but in most cases you cannot count on the smartcard (or smartcard-like > device) being in the reader. > Which is why in my opinion this is an ideal case for

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

On 8/30/17, 00:59, "openssl-dev on behalf of Paul Dale" wrote: >My thoughts are that the new RNG API should be made public once it has >been properly designed. We've a chance to get this right, let's take the > time >

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

> -Ursprüngliche Nachricht- > Von: openssl-dev [mailto:openssl-dev-boun...@openssl.org] Im Auftrag von Matt > Caswell > Gesendet: Dienstag, 29. August 2017 16:36 > An: openssl-dev@openssl.org > Betreff: Re: [openssl-dev] Plea for a new public OpenSSL RNG API > > > > On 29/08/17 15:02,

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

> I realize that reseed() not only mixes my “additional input” but also > replaces the entire state. NIST does > not specify interface to “just” mix the “additional input” into the state > without replacing the whole state > with some fresh entropy by calling Get_entropy_input(). Maybe we can

Re: [openssl-dev] Upgrading OpenSSL

I now have Racoon2 working. Steve's comment made me think about the digests used in Racoon2 and I went searching for any commands using SHA1. I found two hardcoded as string "SHA1". I changed it to SHA256 and bobs-your-uncle. I guess this is due to the phasing-out of the SHA1 hash which was not

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

>> I *don’t want* OpenSSL to make *any* estimation of the amount of provided >> entropy. All I want it to do is to mix these bits into the RNG state. It’s >> *my* business how much entropy I’m providing – but I don’t want OpenSSL to >> make any decision regarding pull from other entropy sources

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

➢ > Sure I can. Because the DRBG seeds from the system anyway ➢ You can't assume that will work for all users. And for places where the systesm doen’t have enough randomness, there is nothing we can do. -- openssl-dev mailing list To unsubscribe:

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

On Tue, Aug 29, 2017 at 08:38:09PM +, Blumenthal, Uri - 0553 - MITLL wrote: > > If, based on its value, OpenSSL may decide that it now got “enough” entropy > > and doesn’t need to > > pull more from other sources before serving randomness to requestors – then > > it is harmful. > >

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

➢ But now we just ignore it and assume every bit with get contains 1 ➢ bit of randomness and we're sundenly seriously overestimating the ➢ amount of randomness we're getting. This is a documented public API, ➢ you can't just go and ignore this parameter. Sure I can. Because the

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

> If, based on its value, OpenSSL may decide that it now got “enough” entropy > and doesn’t need to > pull more from other sources before serving randomness to requestors – then > it is harmful. > “Over-confidence” in this value by the caller can negatively impact the > quality of the produced

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

On Tue, Aug 29, 2017 at 06:50:37PM +, Blumenthal, Uri - 0553 - MITLL wrote: > On 8/29/17, 12:45, "openssl-dev on behalf of Salz, Rich via openssl-dev" > wrote: > > ➢ An other problem with the current implemenation is

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

On 8/29/17, 15:22, "openssl-dev on behalf of Salz, Rich via openssl-dev" wrote: ➢ I’d like to suggest that any approach other than “immediately mix the received randomness into the RNG state” is bad. If a user does

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

In message <168cef3c-d655-47bf-9874-048308154...@ll.mit.edu> on Tue, 29 Aug 2017 19:04:48 +, "Blumenthal, Uri - 0553 - MITLL" said: uri> uri> Could you please be more specific wrt. DRBG organization that in your opinion could impact the UI? uri> uri> Are you

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

➢ I’d like to suggest that any approach other than “immediately mix the received randomness into the RNG state” is bad. If a user does RAND_add() now, as opposed to 100 source code lines before, there may be a reason for that. I think the only way to do that in the DRBG model is to treat it

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

On 8/29/17, 11:33, "openssl-dev on behalf of Salz, Rich via openssl-dev" wrote: Could you please be more specific wrt. DRBG organization that in your opinion could impact the UI? > From your use-case:

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

IMHO this interface is a way for the user to improve the quality of the randomness it would get from the given RNG, *not* to replace (or diminish) its other sources. My proposal is to abolish this parameter, especially since now it is simply ignored (and IMHO – for a good reason). That's a

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

uri> Could you please be more specific wrt. DRBG organization that in your opinion could impact the UI? Are you talking about the UI API or something else? No-no-no, just the UI API. I used the term “UI” to emphasize that this is the “public” part of the API, exposed to the

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

➢ IMHO this interface is a way for the user to improve the quality of the randomness it would get from the given RNG, *not* to replace (or diminish) its other sources. My proposal is to abolish this parameter, especially since now it is simply ignored (and IMHO – for a good reason). We

Re: [openssl-dev] Plea for a new public OpenSSL RNG API

On 08/29/2017 01:50 PM, Blumenthal, Uri - 0553 - MITLL wrote: > IMHO this interface is a way for the user to improve the quality of the > randomness it would get from the given RNG, *not* to replace (or diminish) > its other sources. My proposal is to abolish this parameter, especially since >

<    1   2   3   4   5   6   7   8   9   10   >