Nikos Mavrogiannopoulos <[email protected]> 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? > 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? One could also have an rsa_keypair_prepare that takes a pair of private and public keys, instead of calling the other two prepare functions. Similar issues if keys don't match as they are supposed to. Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance. _______________________________________________ nettle-bugs mailing list [email protected] http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
