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
It should be possible to generate CertificateParams from an X509Certificate directly, instead of having to go through DER decode/encode. Also methods like DistinguishedName::from_name are private while they could presumably be public.
The text was updated successfully, but these errors were encountered:
Right now, I think there is zero dependence in the public API on x509-parser types, in other words, we could theoretically replace that crate completely and it wouldn't break user code (outside of potential behaviour changes). Improving interop would prevent that flexibility. Also, a semver breaking upgrade of x509-parser would now be one for rcgen, too.
It should be possible to generate
CertificateParams
from anX509Certificate
directly, instead of having to go through DER decode/encode. Also methods likeDistinguishedName::from_name
are private while they could presumably be public.The text was updated successfully, but these errors were encountered: