Cleaning up non_domain_separated_hpke_encrypt_decrypt cfgs
#254
+7
−14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…pt_decrypt without ffi feature enabled
mulmarta
previously approved these changes
Feb 17, 2025
mulmarta
approved these changes
Mar 4, 2025
tomleavy
approved these changes
Mar 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cleaning up the cfgs so users can use non_domain_separated_hpke_encrypt_decrypt without ffi feature enabled
In the current state, the
cfgs for thenon_domain_separated_hpke_encrypt_decryptflagged-out functions are configured such that they can only be used if a user has theffifeature also enabled. This requires a dependency onsafer_ffi_gen. (This is my mistake, for how I configured these)This PR just changes the configuration to remove this dependency, so users can use the
non_domain_separated_hpke_encrypt_decryptfunctions even withoutffi.