Message-ID: <a70e97cc-335f-2aa5-47fc-880db670694e@enterprisedb.com>
Date: Thu, 16 Dec 2021 12:23:11 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0)
 Gecko/20100101 Thunderbird/91.3.2
Subject: Re: Transparent column encryption
Content-Language: en-US
To: Greg Stark <stark@mit.edu>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
References: <89157929-c2b6-817b-6025-8e4b2d89d88f@enterprisedb.com>
 <CAM-w4HPmmOvLDXEAT8x-SCMz7FTn5BXn_oKU5itXGOMeq-z13A@mail.gmail.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
In-Reply-To: 
 <CAM-w4HPmmOvLDXEAT8x-SCMz7FTn5BXn_oKU5itXGOMeq-z13A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/a70e97cc-335f-2aa5-47fc-880db670694e%40enterprisedb.com>
Precedence: bulk

On 16.12.21 05:47, Greg Stark wrote:
>> In the server, the encrypted datums are stored in types called
>> encryptedr and encryptedd (for randomized and deterministic
>> encryption).  These are essentially cousins of bytea.
> 
> Does that mean someone could go in with psql and select out the data
> without any keys and just get a raw bytea-like representation? That
> seems like a natural and useful thing to be able to do. For example to
> allow dumping a table and loading it elsewhere and transferring keys
> through some other channel (perhaps only as needed).

Yes to all of that.