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

Re: Specification for Trusted PLs?

From: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Specification for Trusted PLs?
Date: 2010-05-21 18:53:19
Message-ID: 1101a8c1f5c847a2058591fbc70800d0@biglumber.com (view raw or flat)
Thread:
Lists: pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> Well, the best way to define what a trusted language can do is to
> define a *whitelist* of what it can do, not a blacklist of what it
> can't do. That's the only way to get a complete definition. It's then
> up to the implementation step to figure out how to represent that in
> the form of tests.

No, that's exactly backwards. We can't define all the things a language 
can do, but we can certainly lay out the things that it is not supposed to.

- -- 
Greg Sabino Mullane greg(at)turnstep(dot)com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201005211452
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAkv21oIACgkQvJuQZxSWSsg8lQCdFKNXO5XWD5bJ0lQAx3prFYGW
5CYAnjHiuwKVAxvwjl/clyiwCtXCVvr0
=5tSD
-----END PGP SIGNATURE-----



In response to

Responses

pgsql-hackers by date

Next:From: Stephen FrostDate: 2010-05-21 18:57:23
Subject: Re: Specification for Trusted PLs?
Previous:From: Robert HaasDate: 2010-05-21 18:22:33
Subject: Re: Specification for Trusted PLs?

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