Re: How to stop script executions

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: How to stop script executions
Date: 2016-07-26 13:24:45
Message-ID: CAKFQuwadiDCbkaN9VW6qAqqm9=hEw6zZHTgGh-dW0vT8b+Ud=Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Jul 26, 2016 at 9:19 AM, Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> wrote:

> On Tue, Jul 26, 2016 at 6:35 PM, David G. Johnston <
> david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
>> The way to go about prohibiting their usage altogether is specific to
>> your installation method. But by default those languages are not installed
>> into newly created databases and only a superuser can "CREATE EXTENSION" so
>> without superuser intervention uses in the database will be unable to
>> create functions in those languages. If that is an insufficient level of
>> prevention you would have to somehow get your installation of PostgreSQL to
>> not include those core extensions. I'm pretty sure that during compilation
>> you ​can do this. For packaged distributions I do not know what all is
>> involved (i.e., what you have to choose to not install).
>>
>>
>>
> Thanks David !
> Yeah, the extensions for perl and python are not installed. Checked both
> pg_available_extensions & \dx output.
>
> Can I run OS commands without these extensions?
>
>
​Superuser: yes (specifically I'm thinking the COPY FROM PROGRAM command,
but also C language functions)
Ordinary user: not that I can think of.

David J.​

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2016-07-26 13:29:21 Re: How to stop script executions
Previous Message David G. Johnston 2016-07-26 13:22:25 Re: How to stop script executions