Skip site navigation (1) Skip section navigation (2)

Re: viewing source code

From: "Trevor Talbot" <quension(at)gmail(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com>, "Kris Jurka" <books(at)ejurka(dot)com>, "Merlin Moncure" <mmoncure(at)gmail(dot)com>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, "Bill Moran" <wmoran(at)collaborativefusion(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: viewing source code
Date: 2007-12-19 15:45:06
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
On 12/18/07, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:

> On Tue, 18 Dec 2007 10:05:46 -0600
> "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com> wrote:

> > If we are talking about enhancement requests, I would propose we
> > create a role that can be granted/revoked that enables a user to see
> > dictionary objects like source code.  Secondly, users should be able
> > to see their own code they write but not others unless they have been
> > granted this dictionary role.

> You are likely not going to get any support on an obfuscation front.
> This is an Open Source project :P

Wait, what? This is a DBMS, with some existing security controls
regarding the data users are able to access, and the proposal is about
increasing the granularity of that control. Arbitrary function bodies
are just as much data as anything else in the system.

Obfuscation would be something like encrypting the function bodies so
that even the owner or administrator cannot view or modify the code
without significant reverse engineering. I mean, some people do want
that sort of thing, but this proposal isn't even close.

Where on earth did "obfuscation" come from?

In response to

pgsql-performance by date

Next:From: Roberts, JonDate: 2007-12-19 15:52:31
Subject: Re: viewing source code
Previous:From: Scott MarloweDate: 2007-12-19 15:26:36
Subject: Re: Dual core Opterons beating quad core Xeons?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group