5 Aug
2016
5 Aug
'16
6:52 a.m.
On Fri, 2016-08-05 at 09:56 +0200, Niels Möller wrote:
Nikos Mavrogiannopoulos nmav@redhat.com writes:
That's correct, but it still bugs me as a cost that gets added into busy servers.
But only once per hostkey and server restart, right?
As it is now I do not set the size explicitly and call the prepare function on every RSA operation (sign/decrypt).
What about adding a version of prepare that takes both the public key and the pubkey as in the attached patch?
Makes some sense. But I wonder what the failure mode is if the input keys don't match, so that the rsa_private_key struct ends up with an incorrect size field?
That's correct, but I think that's the responsibility of the caller to supply the corresponding keys.
regards, Nikos