Skip site navigation (1) Skip section navigation (2)

Re: Crypto

From: Marcos Luis Ortiz Valmaseda <mlortiz(at)uci(dot)cu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>, David Fetter <david(at)fetter(dot)org>
Subject: Re: Crypto
Date: 2009-09-19 17:27:00
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
I think the same, These are not arguments to include crypto on the core, due to then all users have to think on this aspect to build a simple database, so we would be obligating to the users to use this module.

I´d let this module on the contrib 


"The hurry is enemy of the success: for that reason.......Be patient"

Ing. Marcos L. Ortiz Valmaseda
Línea Soporte y Despliegue
Centro de Tecnologías de Almacenamiento y Análisis de Datos (CENTALAD)

Linux User # 418229
PostgreSQL User

----- Mensaje original -----
De: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Para: "David Fetter" <david(at)fetter(dot)org>
CC: "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "PG Hackers" <pgsql-hackers(at)postgresql(dot)org>
Enviados: Sábado, 19 de Septiembre 2009 6:33:36 GMT -10:00 Hawai
Asunto: Re: [HACKERS] Crypto 

David Fetter <david(at)fetter(dot)org> writes:
> On Sat, Sep 19, 2009 at 11:50:35AM -0400, Andrew Dunstan wrote:
>> What benefit would we  gain from making general crypto part of the
>> core?

> People may wish to encrypt things in the database.

That is not an argument why it has to be in core rather than an add-on.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Jeff DavisDate: 2009-09-19 17:48:13
Subject: Re: WIP: generalized index constraints
Previous:From: Tom LaneDate: 2009-09-19 17:21:10
Subject: Standalone backends run StartupXLOG in an incorrect environment

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group