Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A spec probably shouldn't care about whether the key is PKCS1 or PKCS8 encoded #485

Closed
GalRogozinski opened this issue Aug 15, 2024 · 2 comments

Comments

@GalRogozinski
Copy link
Contributor

A spec probably shouldn't care about whether the key is PKCS1 or PKCS8 encoded

We maybe should consider deleting this code

Originally posted by @GalRogozinski in #481 (comment)

@y0sher
Copy link
Contributor

y0sher commented Aug 19, 2024

IMO this SHOULD be something declared in the spec, so this is standardized ( for example across clients ). I agree spec shouldn't care about which implementation to use, but it should tell all client implementers that they should accept a key encoded in some specific format.

@GalRogozinski
Copy link
Contributor Author

I agree and I am closing this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants