Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Securing stored procedures and triggers
- From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
- To: "Douglas McNaught" <doug(at)mcnaught(dot)org>
- Cc: fasupport(at)allcoast(dot)net, pgsql-general(at)postgresql(dot)org
- Subject: Re: Securing stored procedures and triggers
- Date: Wed, 31 Oct 2007 13:10:05 -0500
On 10/31/07, Douglas McNaught <doug(at)mcnaught(dot)org> wrote: > The only bulletproof way to do this currently is to write all your > stored functions in C and load them as a shared library. Well, as I pointed out in my post, even that's not bullet-proof. As long as decompilers / debuggers etc... exist, then compiling is just a small barrier to a good hacker. The only way to win is not to play, i.e. keep the code in house.
- Follow-Ups:
- Re: Securing stored procedures and triggers
- From: Douglas McNaught
- Re: Securing stored procedures and triggers
- References:
- Securing stored procedures and triggers
- From: mgould
- Re: Securing stored procedures and triggers
- From: Douglas McNaught
- Securing stored procedures and triggers
- Prev by Date: Re: Automatic schema updates
- Next by Date: Re: getting list of tables from command line
- Previous by thread: Re: Securing stored procedures and triggers
- Next by thread: Re: Securing stored procedures and triggers
- Indexes: