Paul> Does anybody know if (parts of) OpenSSL compile and run on the
Paul> pSos operating system?
Paul> In case it matters: I'm particularly interested in the crypto
Paul> (algorithms, x509, etc.) part of OpenSSL, which could (except
Paul> BIO, ...?) be quite portable I guess.
OpenSSL (0.9.
Title: RSA_Sign difference for MD5 hash and SHA1 hash
Hi,
Is there a difference for RSA_Sign for MD5 hash and SHA1 hash? I am working on VPN Software and in IKE with digital certificate (with RSA keys), it works fine when hash algo is SHA1 but it does not work when hash algo is MD5. On remot
Does anybody know if (parts of) OpenSSL compile and run on the pSos
operating system?
In case it matters: I'm particularly interested in the crypto (algorithms,
x509, etc.) part of OpenSSL, which could (except BIO, ...?) be quite
portable I guess.
Regards,
Paul
__
After reviewing the email archives for both the developer and user
groups, I have a lot of questions:
- What platforms are being FIPS certified?
- Is it FIPS 140-2?
- What version of OpenSSL does it correspond to? 0.9.7b?
- Are both the static libraries and dynamic libraries to be certified?
If no
Nils Larsch wrote:
I think the problem may be the less-than-intuitive API.
suggestion for improvement ?
Experience is the best teacher. Apart from that, a total rewrite
in C++ ;-) Object-oriented code written in C (SSLeay, BSAFE, etc.)
is inherently icky.
I'm coming close to the end of the work to get OpenSSL FIPS-140ed. So,
if people have comments/changes/concerns, they'd better get a move on
and clue me in, because once its done we can't change it.
Cheers,
Ben.
--
http://www.apache-ssl.org/ben.html http://www.thebunker.net/
"There is no
Michael Sierchio wrote:
Nils Larsch wrote:
Is it true that for a given P & g, I would always get the same public
key
No, the private key is (should be) a random number => you get a different
public key for each invocation of DH_generate_key
Not quite, no. In fact, DH would be pretty useless