-
Notifications
You must be signed in to change notification settings - Fork 143
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
Public functions for validating keys #409
Comments
@ilammy would you mind to comment here if some language wrappers have these updates already? maybe Rust? |
Yeah, only Rust wrapper makes a good use of the exported API (duh...) Overall availability status:
As for particular languages and provided API... C core
Python
Ruby
C++
Rust
|
I recall that strong key types is one of the desired features across all wrappers. Thus it seems to me that the best way to provide this API would be to integrate it with those new type constructors, like it's done in Rust. Then the users would be forced to validate the keys and ensure that they have correct kinds before passing them to Themis. We could also provide freestanding validation functions (like existing |
I have a feeling that we've done here a lot, but no further public updates are planned, so I close this issue. |
The master branch currently contains new (semi-private) API for key validation and inspection:
themis_is_valid_asym_key
themis_get_asym_key_kind
It may be useful across the language wrappers so it should be exported in a consistent way, probably with specific implementations for validating keys for Secure Messages, Secure Session, etc.
The text was updated successfully, but these errors were encountered: