[e-lang] An object-capability subset of Python
toby.murray at comlab.ox.ac.uk
Tue Sep 16 11:57:00 CDT 2008
On Tue, 2008-09-16 at 15:12 +0000, Karp, Alan H wrote:
> Toby Murray wrote:
> > Surely it's not the responsibility of general language developers to
> > ensure the concerns of the "security sideshow" (to quote Linus
> > Torvalds)
> > are given priority. Rather it should be our responsibility to influence
> > the design process of languages if we want to ensure that future
> > revisions will meet our needs (e.g. allow secure ocap subsetting, etc.)
> We are in violent agreement. However, if security knowledgeable people don't know what the proposals are before they are adopted, there will be less chance to have that influence. I'm proposing that people on this list who know of pending language changes post a summary here, so that others can comment. Then it's up to us to prove the value of our position. We may find the language designers indifferent between two versions of a feature, one security enhancing and one security antagonistic.
Sounds fair enough to me.
More information about the e-lang