Add pgsodium getkey script using /dev/urandom and update to 2.0.1 #126
Conversation
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
dragarcia
approved these changes
Jan 17, 2022
hf
pushed a commit
that referenced
this pull request
Jan 23, 2023
* update to pgsodium 2.0.0 * add urandom get key script on db init. * add urandom get key script on db init. * update to pgsodium 2.0.1
damonrand
pushed a commit
to cepro/postgres
that referenced
this pull request
Jun 15, 2025
…pabase#126) * update to pgsodium 2.0.0 * add urandom get key script on db init. * add urandom get key script on db init. * update to pgsodium 2.0.1
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.
What kind of change does this PR introduce?
This adds a pgsodium getkey script which generates a random root key from
/dev/urandomon db init.What is the current behavior?
The current config does not preload pgsodium and cannot load a hidden root key.
What is the new behavior?
This change adds a script that postgres calls on boot to load a new key. I was originally adding this upstream in the
supabase/supabasedocker compose, but I think it makes more sense to make this feature available by default. This is backwards compatible and shouldn't break anything. My only concern would be it hsould only work on linux, bsd, and macos. If this package is expected to run on windows perhaps there is a way to make it optional.Additional context
Add any other context or screenshots.