Are you sure you are using the correct man pages?
There is no reference to mttest.c in the repository anymore.
Pauli
--
Oracle
Dr Paul Dale | Cryptographer | Network Security & Encryption
Phone +61 7 3031 7217
Oracle Australia
From: Charles Mills [mailto:charl...@mcn.org]
Sent:
Yes.
Pauli
--
Oracle
Dr Paul Dale | Cryptographer | Network Security & Encryption
Phone +61 7 3031 7217
Oracle Australia
From: Charles Mills [mailto:charl...@mcn.org]
Sent: Thursday, 19 October 2017 7:20 AM
To: openssl-users@openssl.org
Subject: Re: [openssl-users] Replacing
Sorry - OpenSSL is not what I do every day.
I see in the man pages a reference to crypto/threads/mttest.c. I've got the
1.1.0f tar and the crypto directory does not contain a threads directory.
Where do I find mttest.c?
Thanks,
Charles
--
openssl-users mailing list
To
Wow! Thanks.
You are saying to just drop out this array, and the two
CRYPTO_set_..._callback() functions, and the functions they reference?
Charles
From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
Paul Dale
Sent: Wednesday, October 18, 2017 2:14 PM
To:
OpenSSL 1.1.x handle the locking themselves. You don't need to install the
locking call backs and don't need to provide locking functionality.
Pauli
--
Oracle
Dr Paul Dale | Cryptographer | Network Security & Encryption
Phone +61 7 3031 7217
Oracle Australia
From: Charles Mills
I am migrating a multi-threaded Windows application from OpenSSL 1.0.1h to
1.1.0f.
I am using the Shining Light pre-built Windows DLLs.
The code, which I wrote some time ago, has a statement HANDLE
Comm::sslMutexArray[CRYPTO_NUM_LOCKS];
The array is referenced by my
➢ I used libcrypto to parse out the OCSP URL from the certificate validate
it against a whitelist of valid OCSP URLs, send an OCSP request and
validate the response and its signature against a custom certificate
store, and then parse out the result.
Two points on that:
➢ -
Hi,
I have an application which wants to do verification of a certificate.
Not in the context of a context or a signature, but simply to verify if
the certificates are still valid and from a source that is correct in
the context in which the application runs.
I used libcrypto to parse out the
On 17/10/17 21:27, Chris Bare wrote:
> I have the following code:
>
> setup_ssl (char *server_name, char *port, SSL_CTX *ctx)
> {
> BIO *output = BIO_new_ssl_connect (ctx);
> if (!output)
> {
> return (NULL);
> }
> BIO_get_ssl (output, );
> SSL_set_mode (ssl,
