Am Montag, 28. Januar 2008 schrieb Tom Lane:
> My recollection is that certain cryptography laws make hooks for crypto
> just as problematic as actual crypto code. We'd have to tread very
> carefully --- "general purpose" hooks are OK but anything narrowly
> tailored to encryption purposes would be a hazard.
PostgreSQL already has built-in support for SSL and Kerberos, so it is already
infested with enough weaponized code to fail most applicable regulations.
In response to
pgsql-patches by date
|Next:||From: Peter Eisentraut||Date: 2008-01-29 14:21:42|
|Subject: Re: WIP: plpgsql source code obfuscation|
|Previous:||From: Kenneth Marshall||Date: 2008-01-29 13:40:38|
|Subject: Re: [PATCHES] Proposed patch: synchronized_scanningGUCvariable|