We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is a security feature. This prevents an attacker from directly reading the contents of a database without decrypting it first.
Please see https://discord.com/channels/902568124350599239/970336107206176768/1014654616442511523 Apparently this was supported in the now defunct GoLang version of SurrealDB.
TiKV, which SurrealDB supports as a KV backend, supports encryption at rest (see https://docs.pingcap.com/tidb/stable/encryption-at-rest#tikv-encryption-at-rest)
See: https://discord.com/channels/902568124350599239/970336107206176768/1014635769865977937
v1.0.0-beta.7
No response
The text was updated successfully, but these errors were encountered:
It would also be nice if SurrealDB Website's features page mentioned this as a 'Planned' feature.
Sorry, something went wrong.
Please take a look at this again
Anything going on this?
https://github.com/orgs/surrealdb/discussions/2190
No branches or pull requests
Is your feature request related to a problem?
This is a security feature. This prevents an attacker from directly reading the contents of a database without decrypting it first.
Describe the solution
Please see https://discord.com/channels/902568124350599239/970336107206176768/1014654616442511523
Apparently this was supported in the now defunct GoLang version of SurrealDB.
Alternative methods
TiKV, which SurrealDB supports as a KV backend, supports encryption at rest (see https://docs.pingcap.com/tidb/stable/encryption-at-rest#tikv-encryption-at-rest)
See: https://discord.com/channels/902568124350599239/970336107206176768/1014635769865977937
SurrealDB version
v1.0.0-beta.7
Contact Details
No response
Is there an existing issue for this?
Code of Conduct
The text was updated successfully, but these errors were encountered: