Crypt::OpenSSL::RSA->new_public_key does not accept a x.509 public key

mgr007 has asked for the wisdom of the Perl Monks concerning the following question:

Hi,

I'm trying to verify a xml signed document. Reading the x.509 certificate works fine, as well as extracting the public key. But if try to read the key with

Crypt::OpenSSL::RSA->new_public_key

I will get the error message

RSA.xs:178: OpenSSL error: expecting an rsa key at blib/lib/Crypt/OpenSSL/RSA.pm (autosplit into blib/lib/auto/Crypt/OpenSSL/RSA/new_public_key.al) line 91, <STDIN> line 1.

My code is:

...

$x509 = Crypt::OpenSSL::X509->new_from_string($cert);
$rsa = Crypt::OpenSSL::RSA->new_public_key($x509->pubkey);
...
[download]

$x509->pubkey seems correctly pem encoded (starting with "-----BEGIN PUBLIC KEY-----" ) and comes from a http://www.w3.org/2000/09/xmldsig signature compliant certificate.

Is there a difference between a rsa public key and a x.509 public key ?

What's the problem ? Do you have an idea ?

Comment on Crypt::OpenSSL::RSA->new_public_key does not accept a x.509 public key Select or Download Code

Replies are listed 'Best First'.
Re: Crypt::OpenSSL::RSA->new_public_key does not accept a x.509 public key by CountZero (Bishop) on Sep 16, 2015 at 19:41 UTC
What does the "Public Key Algorithm" field of the X.509 certificate say? CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James My blog: Imperial Deltronics	[reply]

Replies are listed 'Best First'.

Re: Crypt::OpenSSL::RSA->new_public_key does not accept a x.509 public key
by CountZero (Bishop) on Sep 16, 2015 at 19:41 UTC

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

My blog: Imperial Deltronics

[reply]