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
Currently DSA public keys are encoded as integers because RFC 3279 defines DSA public key encoding in that way. Unfortunately most Python crypto libraries don't natively support this (ex. load_der_public_key).
My suggestion is to use the SubjectPublicKeyInfo ASN1 definition from RFC 5280 to encode the DSA public key in a format that is more universally implemented in other crypto libraries. The proposed change would look something like this:
Let me know if you think this is the correct way to solve the problem, or if you have other ideas for how this should be handled. I'm open to creating a PR for this if you feel this solution is the correct approach.
The text was updated successfully, but these errors were encountered:
So I wouldn't replace encode_dsa_public_key and instead I would say write a generic encode_public_key that was able to generate a PublicKeyInfo for many types of keys that could be tested against load_der_public_key.
Currently DSA public keys are encoded as integers because RFC 3279 defines DSA public key encoding in that way. Unfortunately most Python crypto libraries don't natively support this (ex. load_der_public_key).
My suggestion is to use the SubjectPublicKeyInfo ASN1 definition from RFC 5280 to encode the DSA public key in a format that is more universally implemented in other crypto libraries. The proposed change would look something like this:
Let me know if you think this is the correct way to solve the problem, or if you have other ideas for how this should be handled. I'm open to creating a PR for this if you feel this solution is the correct approach.
The text was updated successfully, but these errors were encountered: