Skip to content
This repository has been archived by the owner on Apr 7, 2021. It is now read-only.

Need help with DB_ENCRYPTION_VERSIONING=false in .env file #40

Open
kalessil opened this issue Jan 8, 2019 · 3 comments
Open

Need help with DB_ENCRYPTION_VERSIONING=false in .env file #40

kalessil opened this issue Jan 8, 2019 · 3 comments

Comments

@kalessil
Copy link

kalessil commented Jan 8, 2019

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 file
DB_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?

@Cypher1983
Copy link

Has there been any update on this, I am trying to achieve the same result.

@austinheap
Copy link
Owner

@kalessil @Cypher1983 -- Can you provide a reproducible example? Want to make sure I'm following correctly.

@kalessil
Copy link
Author

kalessil commented Nov 22, 2019

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants