I just got the OpenSSL ocsp tool option -rmd for specifying the digest
algorithm in signature.
This option is described at the below page,
https://www.openssl.org/docs/manmaster/man1/openssl-ocsp.html
Just out of curiosity, why isn't it at the following man page?
https://www.openssl.org/docs/man1
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
(I'm not an OpenSSL developer, but I know enough of development
processes to explain what I see here. Actual OpenSSL developers
should correct me if I'm wrong.)
Most likely, yes this is currently expected. Since it's a dev branch,
not a release branch, it's not expected to have everything intern
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
MacOS 10.15.5, Xcode-11.5, current OpenSSL master (3.0 dev)
Is this expected:
genpkey: Error setting ec_param_enc:explicit parameter:
C00D090F0100:error::digital envelope
routines:legacy_ctrl_str_to_param:command not
supported:crypto/evp/pmeth_lib.c:1011:
../../util/wrap.pl ../../apps/open
Hello,
your first help in this project, helps much, but now some weeks later,
there is a new problem, and I cannot find any tipps via google.
For all the coding a have looked into the openssl examples.
I create a private key per code, the "openssl rsa -in
test_privatekey.pem -check" is fine
I c
