Bruce, thanks for your hint. Well, we use self-generated keys that we basically get from a self-written SSL-uding Windows tool which gives me just the modulus. The output of that tool is created by BN_bn2hex(), so I am wondering why I just can't read it without these problems. Currently, I have found some PEM routines (not the docu, just an usage example, so if anyone got a pointer for me, he's always welcome) which perform input and output of public keys, but they include their keys in a ---BLAHBLAH--- ... ---ENDBLAHBLAH--- framework. As a solutiuon for my problems has to be found quickly, I am going to use these fuctions for key generation (yep, I will modify that Windows tool) and key-reading. Nevertheless, if anybody still has a hint for me, please drop me a mail. Thanks in advance. -----Ursprüngliche Nachricht----- Von: bruce cartland [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 20. März 2001 07:15 An: [EMAIL PROTECTED] Betreff: Re: How to read a hexadecimal public key modulus value? I've seen this when the key has been completely wrong (don't know why the 3 bits set to 0). Where are you getting the keys from? Some sources (such as some (?) smartcards) invert all data. You could try reversing the byte stream. Is the exponent set correctly (BN_set_word I think)? Before using externally defined data, test your code using OpenSSL command line tools and generated keys and data (genrsa, rsautl, rsa). One of these can be used to dump the modulus. bruce ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
