New created table is not encrypted #155
Answered
by
dAdAbird
gurucubano
asked this question in
Q&A
-
What I've done wrong or missed: I followed exactly https://github.com/Percona-Lab/pg_tde?tab=readme-ov-file
Created a new table 'd02ben_enc':
|
Beta Was this translation helpful? Give feedback.
Answered by
dAdAbird
Mar 28, 2024
Replies: 2 comments
-
Hi @gurucubano For example: CREATE TABLE albums (
album_id INTEGER GENERATED ALWAYS AS IDENTITY PRIMARY KEY,
artist_id INTEGER,
title TEXT NOT NULL,
released DATE NOT NULL
) USING pg_tde; It is quite unclear from the docs and the Readme. We'll update it. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
ImTheKai
-
El día jueves, marzo 28, 2024 a las 09:27:15a. m. -0700, Andrew Pogrebnoi escribió:
Hi @gurucubano
You have to specify `USING pg_tde` during the table creation for it to be encrypted. Otherwise it will be created as the unseal Postgres table.
For example:
```sql
CREATE TABLE albums (
album_id INTEGER GENERATED ALWAYS AS IDENTITY PRIMARY KEY,
artist_id INTEGER,
title TEXT NOT NULL,
released DATE NOT NULL
) USING pg_tde;
```
Thanks, I will test it tomorrow (today I'm off).
It is quite unclear from the docs and the Readme. We'll update it.
I will try to help on this, pointing out what's unclear for me.
Short questions:
1) How the encryption is done? GnuPG?
2) Is there a way to read / export the rows in encrypted form?
matthias
… --
Reply to this email directly or view it on GitHub:
#155 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
--
Matthias Apitz, ✉ ***@***.***, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @gurucubano
You have to specify
USING pg_tde
during the table creation for it to be encrypted. Otherwise it will be created as the unseal Postgres table.For example:
It is quite unclear from the docs and the Readme. We'll update it.