Received: from localhost (unknown [200.46.204.187])
	by postgresql.org (Postfix) with ESMTP id D95682E3E08
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Wed, 19 Dec 2007 11:45:14 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024)
	with ESMTP id 39317-03 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Wed, 19 Dec 2007 11:45:02 -0400 (AST)
Received: from wr-out-0506.google.com (wr-out-0506.google.com
 [64.233.184.236])
	by postgresql.org (Postfix) with ESMTP id EFB042E3E19
	for <pgsql-performance@postgresql.org>;
	Wed, 19 Dec 2007 11:45:08 -0400 (AST)
Received: by wr-out-0506.google.com with SMTP id 58so2364645wri.10
	for <pgsql-performance@postgresql.org>;
	Wed, 19 Dec 2007 07:45:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=ACKDAQntPHbdhb8vygWnvIGt8aPf+Bj9RxLbSy2M5aQ=;
	b=NyPeNSl/ZZRf34LvRV1i4BnbsEOg7+8J2IZJx2/CdlM7c9DzkteLssx79webA6kk/D+NJMkuvGUHNmMJCuWb2m0Qu/ENm7AEWJM2OWgL4CpPRR2X8oP/I0DGWo6BF28Nm2r+rnYz58kZv1ci2ol1Q/o+F0PYKXHwugXlhNyr5Hw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=fESakD15KBmyLYYqVrcBEoMg2ioaILdrKgjL2FvkzFjC70i4zpdKtwp+FJR27yuMxDq3ZD7xELHav8khIsAXSB5raujBw6/Ex/rIJKxWv9kG5SiXr701TbrI3wR/VkvEGJl3D4/O1RhKATn38hAmyqq6rg5+4gj422d5P6kF//c=
Received: by 10.142.180.17 with SMTP id c17mr1634258wff.144.1198079106618;
	Wed, 19 Dec 2007 07:45:06 -0800 (PST)
Received: by 10.143.158.2 with HTTP; Wed, 19 Dec 2007 07:45:06 -0800 (PST)
Message-ID: <90bce5730712190745g59ce2484hdc0a05bee406804e@mail.gmail.com>
Date: Wed, 19 Dec 2007 07:45:06 -0800
From: "Trevor Talbot" <quension@gmail.com>
To: "Joshua D. Drake" <jd@commandprompt.com>
Subject: Re: viewing source code
Cc: "Roberts, Jon" <Jon.Roberts@asurion.com>, "Kris Jurka" <books@ejurka.com>,
	"Merlin Moncure" <mmoncure@gmail.com>,
	"Jonah H. Harris" <jonah.harris@gmail.com>,
	"Bill Moran" <wmoran@collaborativefusion.com>,
	pgsql-performance@postgresql.org
In-Reply-To: <20071218105249.6a1a4c31@commandprompt.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: 
 <1A6E6D554222284AB25ABE3229A92762112A17@nrtexcus702.int.asurion.com>
	<20071218105249.6a1a4c31@commandprompt.com>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200712/281
X-Sequence-Number: 28097

On 12/18/07, Joshua D. Drake <jd@commandprompt.com> wrote:

> On Tue, 18 Dec 2007 10:05:46 -0600
> "Roberts, Jon" <Jon.Roberts@asurion.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?