Re: Generating unique session ids

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tomasz Ostrowski <tometzky(at)batory(dot)org(dot)pl>, Lexington Luthor <Lexington(dot)Luthor(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Generating unique session ids
Date: 2006-07-27 15:40:22
Message-ID: 44C8DE66.60207@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alvaro Herrera wrote:
> Tom Lane wrote:
>
>>> * Any database user is most of the time able to read function
>>> bodies, so anybody who is able co connect to your database will be
>>> able to get your 'secret_salt' and then predict session id's.
>> Yeah, it's not clear where to hide the secret.
>
> In a memfrob'ed (or something better probably) area in a C function?

You could also do it in a untrusted plperl or plpython function.

Joshua D. Drake

--

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Richard Huxton 2006-07-27 15:42:25 Re: Permissions to connect to postgres database
Previous Message Jasbinder Bali 2006-07-27 15:32:15 Permissions to connect to postgres database