Re: Two-way encryption

Поиск
Список
Период
Сортировка
От Toby Corkindale
Тема Re: Two-way encryption
Дата
Msg-id 1807730134.323269.1404263427691.JavaMail.zimbra@strategicdata.com.au
обсуждение исходный текст
Ответ на Two-way encryption  (Patrick Simcoe <patricksimcoe49@gmail.com>)
Ответы Re: Two-way encryption  (Kevin Grittner <kgrittn@ymail.com>)
Список pgsql-general
----- Original Message -----
> From: "Patrick Simcoe" <patricksimcoe49@gmail.com>
> To: pgsql-general@postgresql.org
> Sent: Wednesday, 2 July, 2014 1:42:04 AM
> Subject: [GENERAL] Two-way encryption
>
> I have a question regarding two-way encryption data for specific columns.
>
> Does anyone have a technique or recommendation for two-way encryption which
> somehow obfuscates the decrypt key so that it isn't easily retrievable from
> the database or the application source code? We've already considered (a)
> letting users hold the decrypt key and (b) obfuscating the decrypt key with
> the user's own (one-way encrypted) password, but neither of these
> approaches are viable for us.


If you want the application to be able to decrypt the data automatically, then it has to hold the decryption key
somewhere.There's really no way around that. 
(Except getting humans to enter the key, but they get bored of typing passwords pretty quickly, and then post-it notes
andkeyboard macros end up storing your secret keys instead of relatively-secure server filesystems) 


В списке pgsql-general по дате отправления:

Предыдущее
От: Jeff Janes
Дата:
Сообщение: Re: what specifically does vacuum have to scan / why does it need to rescan the same indexes many, many times
Следующее
От: Alex Hunsaker
Дата:
Сообщение: Re: pl/perl and recent perl versions - failing to load internal modules