OpenSSL provider question

Hi,I want to develop a RSA provider that uses an external HW chip to do the RSA encryption/decryption. The HW chip supports several RSA keys. 1) How can pass information to the provider which key to use? How about information about which key public or private should be used?2) Asymmetrical algor

Re: Question about migrating from d2i_ECPrivateKey() to d2i_PrivateKey(EVP_PKEY_EC, ...)

On Tue, Nov 22, 2022 at 11:09:07AM -0600, Nico Williams wrote: > > Not exactly, PKCS#8-based typing is used in d2i_PKCS8_PRIV_KEY_INFO() > > (for unencrypted PKCS#8 blobs, so no password callback). The > > d2i_PrivateKey() function takes an explicit pkey_type instead. > > Hmmm, well, d2i_Private

Re: Question about migrating from d2i_ECPrivateKey() to d2i_PrivateKey(EVP_PKEY_EC, ...)

On Tue, Nov 22, 2022 at 11:09:07AM -0600, Nico Williams wrote: > > Not exactly, PKCS#8-based typing is used in d2i_PKCS8_PRIV_KEY_INFO() > > (for unencrypted PKCS#8 blobs, so no password callback). The > > d2i_PrivateKey() function takes an explicit pkey_type instead. > > Hmmm, well, d2i_Private

Re: Question about migrating from d2i_ECPrivateKey() to d2i_PrivateKey(EVP_PKEY_EC, ...)

On Sun, Nov 20, 2022 at 02:12:34PM -0600, Nico Williams wrote: > > Generally, I would expect d2i_... to automatically detect the algorithm > > when tagged with a suitable OIDs, and so d2i_AutoPrivateKey() could > > often work, but if you know the expected key type, you can ask for > > that explici

Re: Question about migrating from d2i_ECPrivateKey() to d2i_PrivateKey(EVP_PKEY_EC, ...)

On Fri, Nov 18, 2022 at 11:33:08PM -0600, Nico Williams wrote: > On Fri, Nov 18, 2022 at 04:53:44PM -0600, Nico Williams wrote: > > I can't use d2i_PrivateKey() because that requires an existing > > EVP_PKEY * that has the group already set. > > Although, that's just what's documented. From code

Re: OpenSSL 3 ECC Key use question

What do you need the NID for? Maybe the code could be changed to use names instead of NIDs? The NIDs are somehow legacy thing that might eventually be completely internal at some point. However, if you need the NID, you should be able to use OBJ_sn2nid() to obtain the NID if the curve name is in t

OpenSSL 3 ECC Key use question

Hi, How can I get the nid from the curve name for a EC key in OpenSSL 3? I'm porting code from OpenSSL 1.0.2. I'm converting this: ecc_curve_type = EC_GROUP_get_curve_name(EC_KEY_get0_group((const EC_KEY *)eckey)); if(ecc_curve_type == NID_undef) { to EVP_PKEY_get_utf8_string_

Re: Question about thread safety and SSL_CTX* and its SSL*

> Perhaps you're freeing some objects that are owned by the library, or > continuting to use objects that the library owned and freed. > >> My question is: Is my app thread safe ? I wonder, because I am facing >> random null deref. If I create a `SSL_CTX` for each thr

Re: Question about thread safety and SSL_CTX* and its SSL*

going to use its `SSL` object for establishing some TLS > connections. `SSL` objects never get destroyed, instead I use > `SSL_clear` for kind of recycling them. Perhaps you're freeing some objects that are owned by the library, or continuting to use objects that the library owned and freed.

Question about thread safety and SSL_CTX* and its SSL*

the ownership of a single `SSL`. Finally, each pthread is going to use its `SSL` object for establishing some TLS connections. `SSL` objects never get destroyed, instead I use `SSL_clear` for kind of recycling them. My question is: Is my app thread safe ? I wonder, because I am facing random null

question about trsut root CA, ocsp responder cert, requester singer cert, and issuer cert

I know that we need * ocsp responder cert for verifying the signature of ocsp response, * CA issuer cert to generate CERTID for ocsp request and * ocsp requestor can choose to sign ocsp request using a signer certificate. But instead of having users set that as 3 different settings, I am thinking

error:0308010C:digital envelope routines::unsupported & other EVP_PKEY question

/5p7MRGGK I also have another question regarding EVP_PKEY structures since OpenSSL 3.0. In OpenSSL 1.1.1 my RSA private and public keys were stored separately in RSA structures. Since OpenSSL 3.0, the RSA structure is deprecated along with all functions that accepted them as arguments. Everything now

Re: AES and EVP_CIPHER question

On 17/05/2022 16:25, Philip Prindeville wrote: Thanks, and for 1.1.x? There's nothing equivalent in 1.1.x AFAIK. Matt

Re: AES and EVP_CIPHER question

> On May 17, 2022, at 4:32 AM, Matt Caswell wrote: > > > > On 16/05/2022 23:48, Philip Prindeville wrote: >> Sorry, I shouldn't have phrased that inartfully. >> There is no EVP_CIPHER_CTX_get_padding(), so how does one achieve something >> analogous? > > > From 3.0, assuming you are using

Re: AES and EVP_CIPHER question

On 16/05/2022 23:48, Philip Prindeville wrote: Sorry, I shouldn't have phrased that inartfully. There is no EVP_CIPHER_CTX_get_padding(), so how does one achieve something analogous? From 3.0, assuming you are using provided ciphers (i.e. not engine ones), then OSSL_CIPHER_PARAM_PADDING

Re: AES and EVP_CIPHER question

Sorry, I shouldn't have phrased that inartfully. There is no EVP_CIPHER_CTX_get_padding(), so how does one achieve something analogous? > On May 16, 2022, at 1:00 PM, Philip Prindeville > wrote: > > Thanks. That fixed the return value of EVP_CipherFinal(). > > Is there a reciprocal EVP_CIP

Re: AES and EVP_CIPHER question

Thanks. That fixed the return value of EVP_CipherFinal(). Is there a reciprocal EVP_CIPHER_CTX_get_padding() method to find out what the default padding method is for ECB? > On May 16, 2022, at 12:41 AM, Tomas Mraz wrote: > > The EVP_CIPHER_CTX_set_padding(ctx, 0) must be called after the >

Re: AES and EVP_CIPHER question

The EVP_CIPHER_CTX_set_padding(ctx, 0) must be called after the EVP_CipherInit() to have an effect. Also what is the AST_CRYPTO_AES_BLOCKSIZE value? Is it in bits (i.e, 128)? Also res should be initialized to -1 so you do not return uninitialized value on error. Tomas Mraz On Fri, 2022-05-13 at

Re: AES and EVP_CIPHER question

Here's a simple/stupid test program and its output, running on Ubuntu 20.04 LTS: OpenSSL 1.1.1f 31 Mar 2020 EVP_CIPHER_CTX_new returns 0x5627171042a0 EVP_CipherInit returns 1 EVP_CipherUpdate returns 1, outlen = 0 buf: 'Mary had a littl' EVP_CipherFinal returns 0, finallen = 0 buf: 'Mary had a li

Re: AES and EVP_CIPHER question

> On May 13, 2022, at 10:55 AM, Philip Prindeville > wrote: > > > >> On May 13, 2022, at 10:34 AM, Matt Caswell wrote: >> >> >> >> On 13/05/2022 16:49, Philip Prindeville wrote: >>> Hi, >>> I'm trying to rewrite some legacy AES_* code to use EVP_CIPHER_* so it's >>> forward compatible

Re: AES and EVP_CIPHER question

> On May 13, 2022, at 10:34 AM, Matt Caswell wrote: > > > > On 13/05/2022 16:49, Philip Prindeville wrote: >> Hi, >> I'm trying to rewrite some legacy AES_* code to use EVP_CIPHER_* so it's >> forward compatible into 3.x. >> My code, in a nutshell, looks like: >> static int evp_cipher_aes_d

Re: AES and EVP_CIPHER question

On 13/05/2022 16:49, Philip Prindeville wrote: Hi, I'm trying to rewrite some legacy AES_* code to use EVP_CIPHER_* so it's forward compatible into 3.x. My code, in a nutshell, looks like: static int evp_cipher_aes_decrypt(const unsigned char *in, unsigned char *out, unsigned inlen, const

AES and EVP_CIPHER question

Hi, I'm trying to rewrite some legacy AES_* code to use EVP_CIPHER_* so it's forward compatible into 3.x. My code, in a nutshell, looks like: static int evp_cipher_aes_decrypt(const unsigned char *in, unsigned char *out, unsigned inlen, const ast_aes_decrypt_key *key) { EVP_CIPHER_CTX

Re: Question about examples in openssl doc X509_STORE_CTX_verify_cb

On Mon, Mar 14, 2022 at 11:25:51AM -0700, Edward Tsang via openssl-users wrote: > https://www.openssl.org/docs/man1.1.1/man3/X509_STORE_CTX_verify_cb.html > > I am trying to figure out how this example works but it does not seem to > bypass the (use the second example of X509_V_ERR_CERT_HAS_EXPI

Question about examples in openssl doc X509_STORE_CTX_verify_cb

link: https://www.openssl.org/docs/man1.1.1/man3/X509_STORE_CTX_verify_cb.html I am trying to figure out how this example works but it does not seem to bypass the (use the second example of X509_V_ERR_CERT_HAS_EXPIRED) However the caller code ll long res = SSL_get_verify_result( sslCtx ); still

Re: Question about OpenSSL 3.0 and static linking

o what you want. I noticed, though, that the > documentation in INSTALL.md isn't entirely clear on what that does. > > ./config --prefix=$HOME/local/openssl-3.0.1 no-shared no-module > > Cheers, > Richard > > On Tue, 22 Feb 2022 07:37:03 +0100, > Shunichi Shinohar

Re: Question about OpenSSL 3.0 and static linking

22/2/22 5:37 pm, Shunichi Shinohara wrote: Hi List, I have a question about OpenSSL 3.0 and static linking. Short version: Is it possible to include the legacy provider in libcrypt.a? Somewhat long version below. As a background of the question I'm using OpenSSL with Erlang/OTP [1] on Linu

Re: Question about OpenSSL 3.0 and static linking

e: > > Hi List, > > I have a question about OpenSSL 3.0 and static linking. > > Short version: Is it possible to include the legacy provider in libcrypt.a? > > Somewhat long version below. > As a background of the question I'm using OpenSSL with Erlang/OTP [1] on

Re: Question about OpenSSL 3.0 and static linking

There is a define to allow this: STATIC_LEGACY but I don't remember how to specify it on the configuration command line. We should probably turn this on in a no-shared build. Pauli On 22/2/22 5:37 pm, Shunichi Shinohara wrote: Hi List, I have a question about OpenSSL 3.0 and static li

Question about OpenSSL 3.0 and static linking

Hi List, I have a question about OpenSSL 3.0 and static linking. Short version: Is it possible to include the legacy provider in libcrypt.a? Somewhat long version below. As a background of the question I'm using OpenSSL with Erlang/OTP [1] on Linux and want to static link OpenSSL library.

Re: Question About OpenSSL 3.0, FIPS and Solaris Support

The "unadopted" category is not the same as "unsupported".  We'll make an effort but if access to a physical machine is required, we will have to stop.  Whoever reports a problem will like have to assist with fixing it.  Be that by doing builds or writing code. The platform policy page categor

Question About OpenSSL 3.0, FIPS and Solaris Support

Hi, I'm hoping someone can shed some light on something that's confusing me. In the blog post about the FIPS submission it states that one of the platforms that's being tested is "Oracle Solaris 11.4 on Oracle SPARC M8-1"

Re: Question about constness of EVP_PKEY* arguments in public API

On 02/09/2021 16:43, Romain GEISSLER via openssl-users wrote: I am using the following OpenSSL API: EVP_DigestSignInit, EVP_DigestVerifyInit, EVP_PKEY_size, EVP_SealInit, EVP_OpenInit. And it seems these all take an non-const EVP_PKEY* argument. Does it mean that EVP_PKEY* have some internal s

Question about constness of EVP_PKEY* arguments in public API

Hi, I have some piece of software using OpenSSL that works right now on a single thread right now. I am adding a bit more "const" in the code everywhere I can as we want to start using the same code in multithreaded environment, and potentially two threads might sign/verify/encrypt/decrypt usin

Re: Question on "unsupported certificate purpose" error when trying to read the certificate on the web server

hat is EE certificate? > > > On Wed, Jul 21, 2021 at 6:55 PM Viktor Dukhovni < > openssl-us...@dukhovni.org> wrote: > >> On Wed, Jul 21, 2021 at 06:34:03PM -0400, Thejus Prabhu wrote: >> >> > verify error:num=26:unsupported certificate purpose >> &g

Re: Question on "unsupported certificate purpose" error when trying to read the certificate on the web server

:unsupported certificate purpose > > The certificate in question is CA certificate, not an EE certificate. > Specifically, the key usage and Netscape Cert Type signal that its > purpose is exclusively to be a CA, not a TLS server. > > X509v3 Key Usage: critical >

Re: Question on "unsupported certificate purpose" error when trying to read the certificate on the web server

On Wed, Jul 21, 2021 at 06:34:03PM -0400, Thejus Prabhu wrote: > verify error:num=26:unsupported certificate purpose The certificate in question is CA certificate, not an EE certificate. Specifically, the key usage and Netscape Cert Type signal that its purpose is exclusively to be a CA, no

Question on "unsupported certificate purpose" error when trying to read the certificate on the web server

Hi, I am new to openssl and learning how to use it. I am trying to read the self-signed SSL certificate created on a webserver. I am using OpenSSL 1.1.1k on the client machine when I make a request using: openssl s_client -showcerts -connect 192.168.1.200:443 I end up with the following error "*

Re: reg: question about SSL server cert verification

> On 19 Jun 2021, at 10:08 pm, Jakob Bohm via openssl-users > wrote: > >> Differences are observed once the local trust store contains some >> intermediate certificates or the remote chain provides a cross cert for >> which the local store instead contains a corresponding (same subject >> name a

Re: reg: question about SSL server cert verification

On 2021-06-18 17:07, Viktor Dukhovni wrote: On Fri, Jun 18, 2021 at 03:09:47PM +0200, Jakob Bohm via openssl-users wrote: Now the client simply works backwards through that list, checking if each certificate signed the next one or claims to be signed by a certificate in /etc/certs.  This looku

RE: reg: question about SSL server cert verification

2021 07:10 > >> To: openssl-users@openssl.org > >> Subject: Re: reg: question about SSL server cert verification > >> > > And there are a whole bunch of other checks: signature, validity dates, key > > usage, basic constraints... > > Those checks would

Re: reg: question about SSL server cert verification

On Fri, Jun 18, 2021 at 05:37:33PM +0200, Jakob Bohm via openssl-users wrote: > > Also, the correspondence between the peer identity as requested by > > the client, and as represented by the entity certificate, should not > > be done using the CN component of the Subject DN (as OP suggested), > >

Re: reg: question about SSL server cert verification

On 2021-06-18 16:23, Michael Wojcik wrote: From: openssl-users On Behalf Of Jakob Bohm via openssl-users Sent: Friday, 18 June, 2021 07:10 To: openssl-users@openssl.org Subject: Re: reg: question about SSL server cert verification On 2021-06-18 06:38, sami0l via openssl-users wrote: I&#

Re: reg: question about SSL server cert verification

On Fri, Jun 18, 2021 at 03:09:47PM +0200, Jakob Bohm via openssl-users wrote: > Now the client simply works backwards through that list, checking if > each certificate signed the next one or claims to be signed by a > certificate in /etc/certs.  This lookup is done based on the complete > distingu

RE: reg: question about SSL server cert verification

> From: openssl-users On Behalf Of Jakob > Bohm via openssl-users > Sent: Friday, 18 June, 2021 07:10 > To: openssl-users@openssl.org > Subject: Re: reg: question about SSL server cert verification > > On 2021-06-18 06:38, sami0l via openssl-users wrote: > > I'm c

Re: reg: question about SSL server cert verification

On 2021-06-18 06:38, sami0l via openssl-users wrote: I'm curious how exactly an SSL client verifies an SSL server's certificate which is signed by a CA. So, during the SSL handshake, when the server sends its certificate, will the SSL client first checks the `Issuer`'s `CN` field from the x509

reg: question about SSL server cert verification

I'm curious how exactly an SSL client verifies an SSL server's certificate which is signed by a CA. So, during the SSL handshake, when the server sends its certificate, will the SSL client first checks the `Issuer`'s `CN` field from the x509 SSL certificate that it received for example, and comp

Re: openssl verify question

On 2021-06-17 15:49, Viktor Dukhovni wrote: On Sat, Jun 12, 2021 at 10:20:22PM +0200, Gaardiolor wrote: When I compare those, they are exactly the same. But that's the thing, I think server.sig.decrypted should be prepended with a sha256 designator 30 31 30 0d 06 09 60 86 48 01 65 03 04 02 01 0

Re: openssl verify question

On Sat, Jun 12, 2021 at 10:20:22PM +0200, Gaardiolor wrote: > When I compare those, they are exactly the same. But that's the thing, I > think server.sig.decrypted should be prepended with a sha256 designator > 30 31 30 0d 06 09 60 86 48 01 65 03 04 02 01 05 00 04 20, which is > missing. I do s

Re: openssl verify question

Hi, On 12/06/21 22:20, Gaardiolor wrote: Hello, My openssl-1.0.2k-21.0.1.el7_9.x86_64 verify fails with HSM-signed certificates. The HSM is causing other issues and is likely misbehaving, I think this is a HSM bug. I'm sure I'm using the correct server.crt and rootca.crt. $ openssl verify

openssl verify question

Hello, My openssl-1.0.2k-21.0.1.el7_9.x86_64 verify fails with HSM-signed certificates. The HSM is causing other issues and is likely misbehaving, I think this is a HSM bug. I'm sure I'm using the correct server.crt and rootca.crt. $ openssl verify -CAfile rootca.crt server.crt server.crt: C

Re: Fwd: Question about RSA key access mechanism

Hi there, Thank you very much for your email. As I was suspecting, I was making a mistake, after following the lead you provided (the function rsa_ossl_mod_exp in the file crypto/rsa/rsa_ossl.c) I started observing hits. I was basically making a mistake with the addresses to watch. Best regards,

Re: Fwd: Question about RSA key access mechanism

On 12/04/2021 09:57, Danis Ozdemir wrote: When I define a watchpoint for that address to verify that it has been accessed when a new client connects to the server and make the server continue, I can't see a hit which means this address hasn't been accessed. *I'm attaching the s_client output

Re: Fwd: Question about RSA key access mechanism

Hi all, Just to see if I can help prompt a response... :-) Danış is working with me to try see how hard it is to reproduce meltdown and snarf a private key. Problem-N of many in doing that is knowing where private key bits are used in OpenSSL - so far gdb seems to be showing no accesses to p,q

Fwd: Question about RSA key access mechanism

Hi all, I hope all is good. My name is Danis Ozdemir, I'm a PhD student in Trinity College (Ireland) and I'm studying computer security. I'm trying to reproduce the meltdown attack as an effort to dive deep into the known attack types with some specific scenarios and "trying to see whether Meltdow

Question on RSA engine and Key strength

Hi All, We are writing a RSA engine for OpenSSL library to handle certificates up to 4096 bytes strength. We do support certificates up to 8k. How to we make engine to handle certificates only up to 4K and others handled by OpenSSL itself. Any help, inputs are appreciated. Thanks and Regards, J

回复: Question: How to using cert files on Android platform?

verification the same code can be reused on firmware and potentially allowing our devices to use the internet in the future. > Almost certainly, but your question is rather oddly phrased and notcompletely > clear. PEM files don't establish connections. Instead of using all certs in the trust s

Re: Question: How to using cert files on Android platform?

e cmd is able to do > that? Almost certainly, but your question is rather oddly phrased and not completely clear. PEM files don't establish connections. Are you looking to capture the entire Ubuntu trust store, or just the specific trust-anchor that is *currently* the ultimate issuer of the

Question: How to using cert files on Android platform?

Hello, I am new to OpenSSL. I am working on a project using JNI+ OpenSSL on an Android App. My task is to create a client to access some web services. Currently, I am able to use the default trust store (/etc/ssl/certs) on Ubuntu18.04 to access the web services. But based on https://stackoverf

Re: Question about SSL_ERROR_WANT_WRITE

10, 2020, 09:14 Cosmin Apreutesei wrote: > Hello, > > I have a question regarding SSL_write() and returning SSL_ERROR_WANT_WRITE > from the write callback. > > _After_ SSL_write() returns with SSL_ERROR_WANT_WRITE (because my write > callback returned SSL_ERROR_WANT_WRITE), can I

Re: Question about SSL_ERROR_WANT_WRITE

On Thu, Dec 10, 2020 at 05:14:00PM +0200, Cosmin Apreutesei wrote: > Hello, > > I have a question regarding SSL_write() and returning SSL_ERROR_WANT_WRITE > from the write callback. > > _After_ SSL_write() returns with SSL_ERROR_WANT_WRITE (because my write &

Question about SSL_ERROR_WANT_WRITE

Hello, I have a question regarding SSL_write() and returning SSL_ERROR_WANT_WRITE from the write callback. _After_ SSL_write() returns with SSL_ERROR_WANT_WRITE (because my write callback returned SSL_ERROR_WANT_WRITE), can I _then_ send the data given to the calback and then call SSL_write

Re: Question related to default RAND usage and update with engine RAND

Have you tried RAND_set_rand_method()? This should replace the RNG with yours. In 3.0, there will be a different scheme and an engine isn’t the ideal way to go. Pauli -- Dr Paul Dale | Distinguished Architect | Cryptographic Foundations Phone +61 7 3031 7217 Oracle Australia > On 1 Dec 2

Question related to default RAND usage and update with engine RAND

Hi All, We are planning to use our own RAND implementation using an engine. What we observe is, during Openssl init, default RAND gets initialized to openssl RAND. Then later we initialize our engine RAND. Even though we make our RAND as default, we see that still openssl uses the initial default

RE: ECDSA certificate question

ec_pmeth.c:331: -Original Message- From: Michael Richardson Sent: Tuesday, September 22, 2020 4:36 PM To: Yan, Bob Cc: openssl-users@openssl.org Subject: Re: ECDSA certificate question Yan, Bob via openssl-users wrote: > Is there a way to generate a ECDSA certificate with SM2

ECDSA certificate question

Hello everybody, Is there a way to generate a ECDSA certificate with SM2 typed public key and ecdsa-with-SM3 as the signature algorithm in openssl 1.1.1x version? Thank you very much! Bob

Re: [EXTERNAL] - Re: Question about TLS 1.3 and openssl -cipher aNULL option

Viktor, Thank you. Yury From: openssl-users on behalf of Viktor Dukhovni Sent: Tuesday, September 8, 2020 10:56 AM To: openssl-users@openssl.org Subject: Re: [EXTERNAL] - Re: Question about TLS 1.3 and openssl -cipher aNULL option On Tue, Sep 08, 2020 at

Re: [EXTERNAL] - Re: Question about TLS 1.3 and openssl -cipher aNULL option

On Tue, Sep 08, 2020 at 05:39:51PM +, Yury Mazin via openssl-users wrote: > I have a question based on the response provided to me: > > My question is why following openssl commands (version 1.1.1f) return > those TLSv1.3 ciphers as offering no authentication and no encryption?

Re: [EXTERNAL] - Re: Question about TLS 1.3 and openssl -cipher aNULL option

On Tue, 2020-09-08 at 17:39 +, Yury Mazin via openssl-users wrote: > Hello, > > I have a question based on the response provided to me: > > My question is why following openssl commands (version 1.1.1f) > return those TLSv1.3 ciphers as offering no authentication and no &

Re: [EXTERNAL] - Re: Question about TLS 1.3 and openssl -cipher aNULL option

Hello, I have a question based on the response provided to me: My question is why following openssl commands (version 1.1.1f) return those TLSv1.3 ciphers as offering no authentication and no encryption? C:\OpenText\iHub20.4-29324643-250C200831\ihub\modules\BIRTiHub\iHub\bin>open

Re: [EXTERNAL] - Re: Question about TLS 1.3 and openssl -cipher aNULL option

Viktor, Thank you for clarifying it. Yury From: openssl-users on behalf of Viktor Dukhovni Sent: Friday, September 4, 2020 12:10 PM To: openssl-users@openssl.org Subject: Re: [EXTERNAL] - Re: Question about TLS 1.3 and openssl -cipher aNULL option On Fri

Re: [EXTERNAL] - Re: Question about TLS 1.3 and openssl -cipher aNULL option

them "support no authentication" (which is not even strictly true, it is the protocol that does not support "no authentication", the TLS 1.3 ciphers are simply silent re certificate algorithm selection), but the "-cipher aNULL" is simply not used when TLS 1.3 is negotiated,

Re: [EXTERNAL] - Re: Question about TLS 1.3 and openssl -cipher aNULL option

From: Benjamin Kaduk Sent: Thursday, September 3, 2020 5:12 PM To: Yury Mazin Cc: openssl-users@openssl.org Subject: [EXTERNAL] - Re: Question about TLS 1.3 and openssl -cipher aNULL option On Thu, Sep 03, 2020 at 11:45:28PM +, Yury Mazin via openssl-users wrote: > He

Re: A question about the “localhost.key” and “localhost.crt” files.

The filenames themselves are insignificant. You can name them anything you want. The apache configuration file(s) contain key/value pairs where SSLCertificateFile specifies the path to the file containing your certificate and SSLCertificateKeyFile specifies the path to the file containing your priv

A question about the “localhost.key” and “localhost.crt” files.

Hello, I think “localhost.crt” and “localhost.key” files using by Apache and they are mandatory for get a HTTPS certificate. Some tools like "Certbot" need them. If these files deleted then how can I regenerate them? Is below command OK? # openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyo

Re: Question about TLS 1.3 and openssl -cipher aNULL option

On Thu, Sep 03, 2020 at 11:45:28PM +, Yury Mazin via openssl-users wrote: > Hello, > > We have a server was originaly using OpenSSL 1.0.2h. > Server is configured to use SSL ciphers as following > ALL:!aNULL:!ADH:!EDH:!eNULL:!EXPORT > When openssl client tries to connect to this server with co

Re: Question about TLS 1.3 and openssl -cipher aNULL option

On Thu, Sep 03, 2020 at 11:45:28PM +, Yury Mazin via openssl-users wrote: > We have a server was originaly using OpenSSL 1.0.2h. Server is > configured to use SSL ciphers as following: > > ALL:!aNULL:!ADH:!EDH:!eNULL:!EXPORT > > When openssl client tries to connect to this server with comma

Question about TLS 1.3 and openssl -cipher aNULL option

Hello, We have a server was originaly using OpenSSL 1.0.2h. Server is configured to use SSL ciphers as following ALL:!aNULL:!ADH:!EDH:!eNULL:!EXPORT When openssl client tries to connect to this server with command openssl s_client -connect localhost:8101-cipher aNULL it fails, because any aNULL ci

[openssl-users] d2i_TYPE() BCP question, distinguish malformed input from malloc error?

I am curious whether anyone has BCP recommentations for distinguishing between (presumably rare) out-of-memory or similar internal resource issues resulting in a NULL return value from d2i_TYPE() (e.g. d2i_X509()), vs. (presumably more common) issues with the input encoding? Does anyone have exper

Re: Question about SSL_key_update

On Thu, Jul 09, 2020 at 06:07:41PM +, Andreas Müller wrote: > Hi, > > I "inherited" our project to support/use TLSv1.3 from a late colleague. We > have a server written in C++ (Windows, Linux) > and clients (Windows, Linux, also written in C++ and also a Java client). > With Java, we use the n

Question about SSL_key_update

Hi, I "inherited" our project to support/use TLSv1.3 from a late colleague. We have a server written in C++ (Windows, Linux) and clients (Windows, Linux, also written in C++ and also a Java client). With Java, we use the native SSLSocket implementation, in Windows we use Schannel and in Lin

Re: Question about OpenSSL .....

Sorry, I forgot to include also a link to INSTALL.md I am linking the preview from PR#12109 again, as it has been improved to leverage Markdown formatting to be more readable: https://github.com/openssl/openssl/blob/be101175badd30402d2e480a79e98ade1343cbfd/INSTALL.md#installing-openssl Same ca

Re: Question about OpenSSL .....

Hello and welcome! > On my system (Debian 10 - Buster) is OpenSSL installed with Version 1.1. > Now, I want to install OpenSSL 3.x, but which is the best way for that? > > Deinstall the old one, or? First, keep in mind that 3.x is still in alpha development stage, so using it as the system-wide l

Question about OpenSSL .....

Hello together, I am new here on this list and I have a question about OpenSSL. On my system (Debian 10 - Buster) is OpenSSL installed with Version 1.1. Now, I want to install OpenSSL 3.x, but which is the best way for that? Deinstall the old one, or? Best regards Zhéxué M.

question about certificate verify

Hi Opessl team We have a root certificate database, there are two root same certificates which have different expire time and thumbprint in the database. We call API "X509_STORE_CTX_init" to load the database first, and then call API "X509_verify_cert" to verify. >From our test result, valid ce

Re: 04/26/2020 openssl smime question...

* I have seen scripts that have the openssl smime option of -inform, or -outform set to DEM. That’s an error. PEM or DER. Interesting mixup. :)

04/26/2020 openssl smime question...

I have seen scripts that have the openssl smime option of -inform, or -outform set to DEM. The documentation for these options cite PEM, DER or SMIME as valid values. Does anyone know where I can find an explanation for DEM? Is it another type of encoding? Thank you, TM

Re: Additional FOM 3.0 question

Excellent.  That's exactly what I was looking for.  Sorry for missing that down at the bottom. Thanks again, Pete On 4/8/20 12:34 PM, Matt Caswell wrote: > > On 08/04/2020 17:11, Pete wrote: >> By any chance has there been any discussion yet regarding what will and >> will not be in the new 3.0 F

Re: Additional FOM 3.0 question

On 08/04/2020 17:11, Pete wrote: > By any chance has there been any discussion yet regarding what will and > will not be in the new 3.0 FOM?  If I recall correctly, the content list > for the now defunct 1.1.1 based FOM was very long and complete.  Our > team is in the planning stages for migrat

Additional FOM 3.0 question

Hello, I know you guys are right now working hard to deliver the first alpha drop very soon, and that this first drop may include the initial functionality of the new FIPS support.  We know that the intention is to obtain one last 140-2 validation for the new 3.0 FOM, and it sounds like it's sti

Re: TLS 1.3 protocol question

Thank you for the clarification. On Sun, Mar 15, 2020 at 1:23 AM Salz, Rich wrote: > The TLS RFC describes the “bytes on the wire” – the syntax for how client > and server communicate, and the semantics of those exchanges. > > > > Is it a specification or standard? Yup both. > > > > Is OpenSSL

Re: TLS 1.3 protocol question

The TLS RFC describes the “bytes on the wire” – the syntax for how client and server communicate, and the semantics of those exchanges. Is it a specification or standard? Yup both. Is OpenSSL implementation of the spec? Yup. What language used in the spec? It’s described in the RFC; see “pre

TLS 1.3 protocol question

Hi, I have been going through RFC's regarding the TLS version 1.3 protocol. I am curious to know does it mean that the TLS version 1.3 protocol is a specification or standard to communicate between client and server? And OpenSSL is a cryptography library to implement TLS version 1.3 protocol? What

Re: Question about handshake error

On Wed, Mar 11, 2020 at 06:06:44PM +, Matt Caswell wrote: > > if (!ssl_security_cert_sig(s, ctx, x, SSL_SECOP_CA_MD | vfy)) > > return SSL_R_CA_MD_TOO_WEAK; > > return 1; > > } > > The exclusion comes in ssl_security_cert_sig - so I think OpenSSL > behaves corr

Re: Question about handshake error

On 11/03/2020 15:31, Viktor Dukhovni wrote: > On Wed, Mar 11, 2020 at 03:12:26PM +, Matt Caswell wrote: > >>> The signature algorithm security level is not expected to be enforced >>> on self-signed certificates (root CAs). How is it happening here? >> >> It isn't. In this case the client

Re: Question about handshake error

On 11/03/2020 17:08, Niki Dinsey wrote: > As for going back to the software vendor, I absolutely want to but don't > hold out too much hope they will change anything.  > I'm basically going to say this: > > The certificate chain contains two redundant root certificates, these > should be remove

Re: Question about handshake error

Thanks Matt for your reply earlier, following your advice I've edited the following line in my openssl.cnf file: CipherString = DEFAULT@SECLEVEL=1 and it now works in s_client and curl: niks@DESKTOP-O2VP5O2:/etc/ssl$ curl https://thankqcrm.accessacloud.com/ /?X-apikey= {"Status":"OK","PageIndex"

Re: Question about handshake error

On Wed, Mar 11, 2020 at 04:57:42PM +, Matt Caswell wrote: > > Matt are you able to confirm whether the below is correct? Perhaps > > I should file a PR to address this if it is... > > I will run some tests to confirm or deny what you think might be > happening. Probably it will be tomorrow b

Re: Question about handshake error

On 11/03/2020 16:56, Viktor Dukhovni wrote: > On Wed, Mar 11, 2020 at 03:12:26PM +, Matt Caswell wrote: > >>> The signature algorithm security level is not expected to be enforced >>> on self-signed certificates (root CAs). How is it happening here? >> >> It isn't. In this case the client

Re: Question about handshake error

On Wed, Mar 11, 2020 at 03:12:26PM +, Matt Caswell wrote: > > The signature algorithm security level is not expected to be enforced > > on self-signed certificates (root CAs). How is it happening here? > > It isn't. In this case the client is openssl but the server is unknown. > The problem

  1   2   3   4   5   6   7   8   9   10   >