+1
Thanks,
M.
On 30. 10. 2012 15:36, Jakob Bohm wrote:
(continuing TOFU posting to match the OP)
A private/public RSA key pair in (n,e)+(n,d) format can be converted
to (n,p,q,e,d,d%(p-1),d%(q-1), (1/q)%p) form by using well known
mathematical steps that are fairly cheap.
A private RSA key in
(continuing TOFU posting to match the OP)
A private/public RSA key pair in (n,e)+(n,d) format can be converted
to (n,p,q,e,d,d%(p-1),d%(q-1), (1/q)%p) form by using well known
mathematical steps that are fairly cheap.
A private RSA key in (n,d) format with no information on e cannot be
converte
I'm afraid RSAKeyValue may represent both public, or private key, but
that's not the point.
The RFC itself defines 2 forms of representation of private key, but
openssl works only
with the second one, the encryption works fine when I pushed zeroes to
the RSA structure,
but I didn't find any ex
On 29 Oct 2012, at 8:44 AM, Miroslav Mikluš wrote:
> The xmldsig (http://www.w3.org/TR/xmldsig-core/#sec-RSAKeyValue)
> use the first form of RSA representation with respect to the :
> http://tools.ietf.org/html/rfc3447#section-3.2
The RSAKeyValue element contains a public key, but the quintuple
