>At the bottom of the man page for x509 it states the following:
The hash algorithm used in the -subject_hash and -issuer_hash options
before OpenSSL 1.0.0 was based on the deprecated MD5
algorithm and the encoding of the distinguished name. In OpenSSL 1.0.0 and
later it is based on a
Having reviewed the git commit for 1.1.1 I notice the following issue:
The environment variables that usually point to the secure administrator
directories (such as "Program Files") are not themselves secured, and not
intended as a secure means of obtaining these directory locations, which
are (b
On 30/07/2019 16:49, Quanah Gibson-Mount wrote:
> As someone who does build OpenSSL on windows, my gist is that if I use a
> non-default OPENSSLDIR I'm ok? Can someone confirm? Thanks!
>
> I.e., I use --openssldir=/opt/symas/ssl
As long as your non-default location is suitably protected to s
As someone who does build OpenSSL on windows, my gist is that if I use a
non-default OPENSSLDIR I'm ok? Can someone confirm? Thanks!
I.e., I use --openssldir=/opt/symas/ssl
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP sol
Hi,
I am trying to (independantly of openssl) generate the hash for a certificate
(the short string
that would be used as the symlink name in the openssl/certs directory).
eg, this command
openssl x509 -in CERT.pem -noout -hash
I am trying to do this because I wanted to know how openssl was calcu
of these versions should
upgrade to OpenSSL 1.1.1.
Referenses
==
URL for this Security Advisory:
https://www.openssl.org/news/secadv/20190730.txt
Note: the online version of the advisory may be updated with additional details
over time.
For details of OpenSSL severity classifications
