| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-patches(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Subject: | Re: WIP: plpgsql source code obfuscation |
| Date: | 2008-01-29 14:19:39 |
| Message-ID: | 200801291519.40196.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
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.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2008-01-29 14:21:42 | Re: WIP: plpgsql source code obfuscation |
| Previous Message | Kenneth Marshall | 2008-01-29 13:40:38 | Re: [PATCHES] Proposed patch: synchronized_scanning GUCvariable |