You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 7, 2021. It is now read-only.
Thank you for a great extension, it's very smooth to integrate!
We have some tables with personal data, which we want to be encrypted. One small consideration was database size and we started configuring header generation, currently configuration looks like this:
# somewhere in .env fileDB_ENCRYPTION_ENABLED=true
DB_ENCRYPTION_PREFIX=:
DB_ENCRYPTION_VERSIONING=false
what produces following results: :versionVERSION-00-01-02typestring[native]... (output from console select command).
And I got stuck with disabling versionVERSION-00-01-02typestring[native] and need help: how to disable it?
The text was updated successfully, but these errors were encountered:
Huh, it was quite a while ago: I wanted to have ":encrypted-data-here" or "encrypted:encrypted-data-here" persisted in database. To replace prefix generation with pre-defined string.
Following official docs didn't bring me firther, so I think we did implement custom encryption behaviour in that project.
That as much details as I can remember.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Thank you for a great extension, it's very smooth to integrate!
We have some tables with personal data, which we want to be encrypted. One small consideration was database size and we started configuring header generation, currently configuration looks like this:
what produces following results:
:versionVERSION-00-01-02typestring[native]...
(output from console select command).And I got stuck with disabling
versionVERSION-00-01-02typestring[native]
and need help: how to disable it?The text was updated successfully, but these errors were encountered: