You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While it looks like it will be fixed, it seems that by including the public key in the certificate, it might save some headache (and computation). Without it, the public key needs to be derived from the private key, which is causing trouble on platforms that don't have fully-featured support.
Our code is essentially:
var priv = KeyFactory.NewKey(KeyAlgorithm.ES256);
var generated = order.Generate(..., priv);
var pfxBuilder = generated.ToPfx(priv);
var cert = pfxBuilder.Build(host, password);
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
See dotnet/runtime#33744
While it looks like it will be fixed, it seems that by including the public key in the certificate, it might save some headache (and computation). Without it, the public key needs to be derived from the private key, which is causing trouble on platforms that don't have fully-featured support.
Our code is essentially:
The text was updated successfully, but these errors were encountered: