bindings/c: Don't forward empty encryption key string#2162
Merged
Conversation
op-sqlite, for example, always passes the remote encryption key:
```
DB opsqlite_libsql_open_sync(std::string const &name,
std::string const &base_path,
std::string const &url,
std::string const &auth_token, int sync_interval,
bool offline, std::string const &encryption_key,
std::string const &remote_encryption_key) {
```
Therefore, ensure that remote encryption key is not null and non-empty
before passing it as part of HTTP requests.
avinassh
approved these changes
Sep 23, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
op-sqlite, for example, always passes the remote encryption key:
Therefore, ensure that remote encryption key is not null and non-empty before passing it as part of HTTP requests.