Re: simply custom variables protection - Mailing list pgsql-patches

From Pavel Stehule
Subject Re: simply custom variables protection
Date
Msg-id BAY114-F2645382BDC3FDCC6388F49F95B0@phx.gbl
Whole thread Raw
In response to simply custom variables protection  ("Pavel Stehule" <pavel.stehule@hotmail.com>)
Responses Re: simply custom variables protection
List pgsql-patches
>
>How does a user protect a custom variable using your code?  I don't see
>any API that would allow that.
>

Every module is responsibile for protectiong own custom variables. Only
module knows if some variable needs protection. And after module
inicialisation module can call ArmorCustomVariable function. From this
moment only superuser can modify this custom variable. If it call
ResetPGVariable() function before then default value is protected. It's
question if test for superuser is necessery, I hope so it's usefull and I
have posibility write security definer function where I can safely modify
custom variables.




>---------------------------------------------------------------------------
>
> >
> > Regards
> > Pavel Stehule
> >
> >
> > >From: Bruce Momjian <bruce@momjian.us>
> > >To: Pavel Stehule <pavel.stehule@hotmail.com>
> > >CC: pgsql-patches@postgresql.org, andrew@dunslane.net,
>tgl@sss.pgh.pa.us
> > >Subject: Re: [PATCHES] simply custom variables protection
> > >Date: Sat, 7 Apr 2007 11:54:13 -0400 (EDT)
> > >
> > >
> > >Pavel, would you remind me how this is useful?
> > >
> >
> >---------------------------------------------------------------------------
> > >
> > >Pavel Stehule wrote:
> > > > Hello
> > > >
> > > > this patch contains function ArmorCustomVariables. This function set
> > >flag
> > > > armored on any custom variable. From this moment only superuser can
> > >change
> > > > this variable.
> > > >
> > > > p.s. use it together with ResetPGVariable()
> > > >
> > > > Regards
> > > > Pavel Stehule
> > > >
> > > > _________________________________________________________________
> > > > Citite se osamele? Poznejte nekoho vyjmecneho diky Match.com.
> > > > http://www.msn.cz/
> > >
> > >[ Attachment, skipping... ]
> > >
> > > >
> > > > ---------------------------(end of
>broadcast)---------------------------
> > > > TIP 1: if posting/reading through Usenet, please send an appropriate
> > > >        subscribe-nomail command to majordomo@postgresql.org so that
>your
> > > >        message can get through to the mailing list cleanly
> > >
> > >--
> > >   Bruce Momjian  <bruce@momjian.us>          http://momjian.us
> > >   EnterpriseDB
>http://www.enterprisedb.com
> > >
> > >   + If your life is a hard drive, Christ can be your backup. +
> > >
> > >---------------------------(end of
>broadcast)---------------------------
> > >TIP 7: You can help support the PostgreSQL project by donating at
> > >
> > >                 http://www.postgresql.org/about/donate
> >
> > _________________________________________________________________
> > Najdete si svou lasku a nove pratele na Match.com. http://www.msn.cz/
>
>--
>   Bruce Momjian  <bruce@momjian.us>          http://momjian.us
>   EnterpriseDB                               http://www.enterprisedb.com
>
>   + If your life is a hard drive, Christ can be your backup. +

_________________________________________________________________
Najdete si svou lasku a nove pratele na Match.com. http://www.msn.cz/


pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: simply custom variables protection
Next
From: Bruce Momjian
Date:
Subject: Re: LIMIT/SORT optimization