DSA_generate_parameters_ex is newer/current and also accepts seed, but EVP_PKEY_paramgen* does not.
If you use EVP_PKEY with an engine it appears to be up to the engine. Otherwise dsa_builtin_paramgen when seed is NULL/0, which it always is for EVP_PKEY, uses a pseudorandom seed and AFAICS you can't get it. Why on earth does windows want seed when exporting a public key, and how is it even possible to provide it? Reqiuring it and using to validate when importing a public key could make some sense, although it's really too late. What really makes sense is when importing a private key, or just parameters. From: [email protected] [mailto:[email protected]] On Behalf Of Leon Brits Sent: Wednesday, February 05, 2014 04:31 To: [email protected] Subject: EVP DSA parameters Hi all, I generate my DSA key pairs using the EVP API. The older API call DSA_generate_parameters() allowed me to set the seed value. With the EVP API this is automatically generated (it seems). Windows however require this seed value when it exports the Public key. So how can I get this "seed" value? Is it fixed? Regards, LJB
