On 12/03/18 22:53, Chris Bare wrote:
> I have a fairly basic server set up based on various examples I've seen.
>
> I run an nmap script I found against it and see only 16 ciphers listed,
> none of which are supported by modern web browsers.
> Yet when I run "openssl ciphers I get a list of 97.
Hi All,
My ultimate goal is to generate an RSA-PSS key that will have the PSS
parameters in the subjectPublicKey section of the TBSCertificate. In order
to do that the first need is a paramfile. Here's the command being used to
to generate the parameter file:
OpenSSL> genpkey -genparam
I have a fairly basic server set up based on various examples I've seen.
I run an nmap script I found against it and see only 16 ciphers listed,
none of which are supported by modern web browsers.
Yet when I run "openssl ciphers I get a list of 97.
I realize some of these are old and deprecated
On 12/03/18 18:39, Erik Forsberg wrote:
>
> There are missing comma's in ssl/t1_trce.c that causes compilation to fail.
> You have to configure with enable-ssl-trace to see it though.
>
> gcc -I. -Iinclude -I../src -I../src/include -fPIC -std=gnu90 -march=core2
> -Wall -O3
There are missing comma's in ssl/t1_trce.c that causes compilation to fail.
You have to configure with enable-ssl-trace to see it though.
gcc -I. -Iinclude -I../src -I../src/include -fPIC -std=gnu90 -march=core2
-Wall -O3 -fomit-frame-pointer -pthread -DFILIO_H -DDSO_DLFCN -DHAVE_DLFCN_H