Skip to content

Commit

Permalink
fixing review comments
Browse files Browse the repository at this point in the history
  • Loading branch information
dutow committed Sep 14, 2023
1 parent f581b9c commit a9c8f7c
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ This is an experimental encrypted access method for Postgres 16.
4. Create the extension: `CREATE EXTENSION pg_tde;`
5. Set the location of the keyring configuration file in postgresql.conf: `pg_tde.keyringConfigFile = '/where/to/put/the/keyring.json'`
6. Create the keyring configuration file (see example keyring configuration)
6. Restart the postgres server
7. Restart the postgres server

## Keyring configuration

Expand All @@ -22,12 +22,13 @@ This is an experimental encrypted access method for Postgres 16.
```

Currently the keyring configuration only supports the file provider, with a single datafile parameter.
This datafile is created and managed by Postgres, the only requirement is that postgres should be able to write to the specified path.

This setup is intended for developmenet, and stores the keys unencrypted in the specified data file.

## Build steps

1. Install libjson-c-dev: `apt install libjon-c-dev`
1. Install libjson-c-dev, for example on Ubuntu/Debian: `apt install libjon-c-dev`
2. Install or build postgresql 16 (see reference commit below)
3. If postgres is installed in a non standard directory, set the `PG_CONFIG` environment variable to point to the `pg_config` executable
4. In the pg_tde directory: `make USE_PGXS=1` and `make USE_PGXS=1 install`
Expand Down

0 comments on commit a9c8f7c

Please sign in to comment.