<HEAD><TITLE>discuss@charon: [730] in "Coldmud discussion meeting"</TITLE>
<H1>[730] in Coldmud discussion meeting</H1></HEAD>
<A HREF="/"><IMG SRC="/i-d.gif" ALT="root"></A>
<A HREF="?730"><IMG SRC="/i-back.gif" ALT="meeting"></A>
<A HREF="/help.html"><IMG SRC="/i-help.gif" ALT="help"></A>
<A HREF="1"><IMG SRC="/i-first.gif" ALT="first"></A>
<IMG SRC="/n-fref.gif" ALT="">
<IMG SRC="/n-pref.gif" ALT="">
<A HREF="729"><IMG SRC="/i-prev.gif" ALT="previous"></A>
<A HREF="731"><IMG SRC="/i-next.gif" ALT="next"></A>
<IMG SRC="/n-nref.gif" ALT="">
<IMG SRC="/n-lref.gif" ALT="">
<A HREF="1641"><IMG SRC="/i-last.gif" ALT="last"></A>
<HR><H2>Possible security hole or something</H2>
<H3>daemon@ATHENA.MIT.EDU (Mon Apr  3 22:19:53 1995
)</H3>
<PRE>
From: crag@serial.MIT.EDU (Robert de Forest )
To: coldstuff@MIT.EDU
Date: Mon, 3 Apr 1995 20:55:06 -0500 (CDT)

Right now parents can add and delete methods on children. This is necessary 
 in order to allow root to define behaviors of all objects. If you are working
 in an environment where builders of parent objects may or may not be trusted
 this can be a bad thing. I would like to think about restricting these and
 other functions to $sys.

I guess Brandon's proposal to 'bind' functions sorta helps with this but we'll
 need to add paramers to things so it will be compile(code, object, name), for
 example.
</PRE>
