From: | Vikas Sharma <shavikas(at)gmail(dot)com> |
---|---|
To: | Vick Khera <vivek(at)khera(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postgresql database encryption |
Date: | 2018-04-22 10:12:19 |
Message-ID: | CAN6gwKwT-oR7g-di0KMp04S6+-UoR7FyqUXhqvuNS0C_D71JZA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks a lot for the valuable information and apologies I didn't provide
specify that the requirement is to encrypt data at rest and in transit.
Regards
Vikas
On Fri, Apr 20, 2018, 21:56 Vick Khera <vivek(at)khera(dot)org> wrote:
> On Fri, Apr 20, 2018 at 11:24 AM, Vikas Sharma <shavikas(at)gmail(dot)com> wrote:
>
>> Hello Guys,
>>
>> Could someone throw light on the postgresql instance wide or database
>> wide encryption please? Is this possible in postgresql and been in use in
>> production?.
>>
>
> For anyone to offer a proper solution, you need to say what purpose your
> encryption will serve. Does the data need to be encrypted at rest? Does it
> need to be encrypted in memory? Does it need to be encrypted at the
> database level or at the application level? Do you need to be able to query
> the data? There are all sorts of scenarios and use cases, and you need to
> be more specific.
>
> For me, using whole-disk encryption solved my need, which was to ensure
> that the data on disk cannot be read once removed from the server. For
> certain fields in one table, I use application level encryption so only the
> application itself can see the original data. Anyone else querying that
> table sees the encrypted blob, and it was not searchable.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tim Cross | 2018-04-22 22:30:25 | Postgres and fsync |
Previous Message | Adrian Klaver | 2018-04-21 20:35:33 | Re: Strange error in Windows 10 Pro |