It would be great help to me, and I am sure for many other people too who are
working with security solutions, if this feature is released as patch before
8.4 release.
Sanjay Sharma> Date: Tue, 1 Apr 2008 22:02:30 -0400> From: [EMAIL PROTECTED]>
To: [EMAIL PROTECTED]> CC: p
tier for password
hashing.
Would replacing md5 with SHA1 in core involve much work?
Sanjay Sharma> To: [EMAIL PROTECTED]> CC: pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] [GENERAL] SHA1 on postgres 8.3 > Date: Wed, 2 Apr 2008
11:38:31 -0400> From: [EMAIL PROTECTED]&
Hello Andrew,
When do you expect this patch to go in production and available for public use?
I would keep an eye for its release.
Sanjay Sharma> Date: Tue, 1 Apr 2008 18:40:24 -0400> From: [EMAIL PROTECTED]>
To: pgsql-hackers@postgresql.org> Subject: [HACKERS] column leve
. These standards
are not as strict as PCI, HIPPA or Sarnabes-Oxley
Compliance with HIPPA regulation requires not only maintaining all records of
who created and updated the record but also who accessed and viewed records,
when and in what context.
Cheers
Sanjay Sharma
> Date: Mon,
CC:
> pgsql-hackers@postgresql.org> > On Sun, Mar 30, 2008 at 2:52 PM, sanjay
> sharma <[EMAIL PROTECTED]> wrote:> > 1. Transparent Data Encryption: The
> column which needs to be stored in> > encrypted form can be specified through
> DDL.> > Hey Sanjay. Based
to go about it.
Sanjay Sharma
Victoria, Canada
_
Technology : Catch up on updates on the latest Gadgets, Reviews, Gaming and
Tips to use technology etc.
http://computing.in.msn.com/
