Riccardo Mottola wrote:
> error calculating SHA on '3c48692aceb44f85cf99c985154c15b79e6baef0'
> got 3c48692aceb44f85cf99c985154c15b79e6baef0 instead of
> 3232affa48628a26653b5aaa44541fd90d690603
> make[1]: *** [test_sha] Error 1
> make[1]: Leaving directory `/usr/src/redhat/BUILD/openssl-0.9.7e/te
Hi,
what about changing the default digest algorithm in apps/x509.c,
apps/req.c and apps/openssl.cnf from md5 to something a bit more
secure like sha-1 ? MD5 shouldn't be used anymore, even by lazy
users who don't explicitly set the digest algorithm.
Nils
___
> As I understand, this is notï a bug. The .pem file containing the RSA
key
> in the cert is there for testing pourposes... not for production. The
> README file says that you should create your own private key. Think that
> this is the server side cert file (with the public and private key), and
Hello,
I tried to build 0.9.7e on my MkLinux box (ppc601 processor). Since the
ultimate goal was producing a RPM package for the distribution, I run
the build process using the acclosed .spec file, but the building fails
at the test phase:
make[2]: Leaving directory `/usr/src/redhat/BUILD/openssl
Do you have an estimation when a stable version of 0.9.8 will be released?
Thomas
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Auftrag von Nils Larsch
> Gesendet: Dienstag, 8. März 2005 10:32
> An: openssl-dev@openssl.org
> Betreff: Re: The breaking of
[EMAIL PROTECTED] wrote:
Hello everybody,
I am not quite sure which list to address so I chose both.
Regarding the news around the "breaking" of SHA1, I wonder if it is planned
or already in work to implement other hash algorithms like SHA256 into
OpenSSL.
sha256 etc. is implemented in 0.9.8-dev
Ni
Hello everybody,
I am not quite sure which list to address so I chose both.
Regarding the news around the "breaking" of SHA1, I wonder if it is planned
or already in work to implement other hash algorithms like SHA256 into
OpenSSL.
Best Regards
Thomas Beckmann
__
