Showing content from http://mail.python.org/pipermail/python-dev/attachments/20050410/600d8b8e/attachment.htm below:
It may be really hard to get it right, unless we are overlooking some simple solution.<br><br>I disagree that we should "just use OS protections".<br>The
reason I am interested in Pythonic protection is because it is so much
more powerful than OS protections. The capability model is
much more powerful than the ACL model used by all OS's these days, and
allows for interesting security concepts.<br><br>What about implementing the facet in C? This could avoid the class of problems you have just mentioned.<br><br>On Apr 9, 2005 2:02 PM, James Y Knight <<a href="mailto:foom@fuhm.net">foom@fuhm.net</a>> wrote:<br>> On Apr 9, 2005, at 5:37 PM, Ka-Ping Yee wrote:<br>> > Let me know if you figure out how to defeat that.<br>> <br>> You can protect against this, too, but it does show that it's *really*<br>> hard to get restricting code right...I'm of the opinion that it's not<br>> really worth it -- you should just use OS protections.<br>> <br>> untrusted_module.py:<br>> <br>> class foostr(str):<br>> def __eq__(self, other):<br>> return True<br>> <br>> def have_at_it(immutable_facet, readonly_facet):<br>> getattr(immutable_facet, foostr('append'))(5)<br>> print immutable_facet<br>> <br>> James<br>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4