It is currently Tue Aug 20, 2019 4:57 am

All times are UTC




Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 100 posts ]  Go to page Previous  1 ... 3, 4, 5, 6, 7
Author Message
 Post subject:
PostPosted: Sat Mar 13, 2010 1:17 pm 
Offline

Joined: Fri Feb 19, 2010 5:04 pm
Posts: 115
Location: England


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Sun Mar 14, 2010 2:39 am 
Offline
Obduction Backer

Joined: Wed May 31, 2006 4:09 am
Posts: 20


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Sun Mar 14, 2010 2:44 am 
Offline

Joined: Tue May 09, 2006 12:33 am
Posts: 1182
Location: British Columbia, Canada


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Sun Mar 14, 2010 5:22 am 
Offline

Joined: Fri Feb 19, 2010 5:04 pm
Posts: 115
Location: England


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Mon Mar 29, 2010 6:15 am 
Offline

Joined: Tue Feb 13, 2007 4:36 pm
Posts: 92
People concerned about how to safely run untrusted python code should take a look at . It describes a way to automatically generate a python interpreter that is incapable of communicating over a network, writing files, or any other sort of I/O except for reading from stdin and writing to stdout. Any untrusted python code (i.e. code bundled with an age) gets run in this sandboxed python interpreter, and all the file I/O and networking are handled on it's behalf by another program that acts as a gatekeeper. This controller program is responsible for implementing any security restrictions, so if the sandboxed python asks the controller to write a file in an unapproved location, it would simply refuse. The controller would be part of Uru, so it would be code that users got from a trusted source. As long as it's security policies aren't too permissive, the most that clients would be risking by running untrusted code bundled with an age is that the age would break, resulting in a crash to the desktop or linking to relto.

Of course, the above only solves the original problem of allowing the client to run untrusted python code. It doesn't solve any of the problems like flymode, but it does mean that we can make an Uru client that you can trust to never infect or destroy your system (provided you get an un-tampered Uru client from a trusted source).


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Mon Jun 07, 2010 9:28 pm 
Offline
Creative Kingdoms

Joined: Tue May 09, 2006 8:06 pm
Posts: 6226
Location: Everywhere, all at once
Consider this a devil's advocate post from an open source believer (and promoter):

For your consideration:

Open-Source Could Mean an Open Door for "Hackers" [quotations added for subjectivity of the word]
http://www.technologyreview.com/computing/25480/

_________________
: : Make a commitment.


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Mon Jun 07, 2010 10:27 pm 
Offline

Joined: Tue May 09, 2006 1:04 am
Posts: 4134
The present configuration is an open door for "hackers" already, so I'm not too concerned :P

_________________
-Whilyam


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Thu Jun 10, 2010 9:29 pm 
Offline

Joined: Wed May 10, 2006 10:54 am
Posts: 11
Location: Mortsel, Antwerpen, Belgium, Europe


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Fri Jun 11, 2010 12:40 am 
Offline

Joined: Fri Feb 19, 2010 5:04 pm
Posts: 115
Location: England


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Sun Sep 19, 2010 10:47 pm 
Offline

Joined: Wed Sep 15, 2010 9:50 pm
Posts: 3
If there's a reason why the community would want to branch the Uru server/client code then how about creating a compile farm where the developers can submit their sourcecode and the compile farm can create the binaries for the client/server. That way anyone who is downloading a game client knows that the sourcecode is also available on the compile farm's webserver and in no way can the developer alter the code after it has been compiled by the server farm to remove any malicious code. In addition, if you're afraid that the developer could later change the server soucecode to include malicious code then what the server farm could do is after it reveals the source code on the web server, it could then inject authentication code into the source before compiling it so that the client could only connect to servers that have the correct authentication code which would have a public/private key pair as part of the encrypted binary. Hopefully that makes a little sense. If not, I can re clarify.

_________________
| KI: 07869362
Debian - Asus P5B Delux motherboard - 3 GB Memory - 9800 GT 1024 GDDR3 PCIE2 - Intel Pentium 4 ES 2800 MHz


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 100 posts ]  Go to page Previous  1 ... 3, 4, 5, 6, 7

All times are UTC


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to: