Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!feeder.news-service.com!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.021 X-Spam-Evidence: '*H*': 0.96; '*S*': 0.00; 'anyway': 0.03; 'server,': 0.12; 'wrote:': 0.14; 'subject:python': 0.15; 'forwards': 0.16; 'hello:': 0.16; 'received:192.168.200': 0.16; 'subject:distribution': 0.16; 'versus': 0.16; 'thanks,': 0.17; 'code.': 0.18; 'large,': 0.19; 'source.': 0.19; 'cc:no real name:2**0': 0.20; 'cc:2**0': 0.20; 'code,': 0.20; '(or': 0.22; 'help.': 0.22; 'code': 0.22; 'header:In-Reply-To:1': 0.22; 'cc:addr:python-list': 0.22; 'subject:code': 0.23; 'guess': 0.26; 'thanks': 0.29; 'server': 0.29; 'effect': 0.29; 'cc:addr:python.org': 0.31; 'standards': 0.31; 'project': 0.32; 'idea': 0.32; 'community': 0.33; 'someone': 0.33; 'fairly': 0.33; 'test': 0.33; 'using': 0.34; 'received:192': 0.34; 'there': 0.35; 'couple': 0.35; 'open': 0.35; 'header:User-Agent:1': 0.35; 'received:192.168': 0.37; 'some': 0.37; 'machine': 0.37; 'decisions': 0.38; 'execute': 0.38; 'resulting': 0.38; 'user': 0.38; 'but': 0.38; 'app': 0.39; 'end': 0.39; 'solution': 0.40; 'play': 0.64; 'online': 0.70; 'lost': 0.71; 'ideas.': 0.73; 'success,': 0.77; 'gain': 0.80; 'battle': 0.84; 'trust.': 0.84 X-IronPort-AV: E=Sophos;i="4.64,373,1301868000"; d="scan'208";a="1797019" X-Virus-Scanned: amavisd-new at zimbra.sequans.com Date: Mon, 16 May 2011 11:36:02 +0200 From: Jean-Michel Pichavant User-Agent: Mozilla-Thunderbird 2.0.0.24 (X11/20100328) MIME-Version: 1.0 To: tyler@tysdomain.com Subject: Re: obviscating python code for distribution References: <87boz3gw5u.fsf@benfinney.id.au> <4dd0a1fc$0$29983$c3e8da3$5496439d@news.astraweb.com> <4DD0B903.4090109@tysdomain.com> In-Reply-To: <4DD0B903.4090109@tysdomain.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: python-list@python.org X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 26 NNTP-Posting-Host: 82.94.164.166 X-Trace: 1305538632 news.xs4all.nl 34849 [::ffff:82.94.164.166]:59078 X-Complaints-To: abuse@xs4all.nl Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:5506 Littlefield, Tyler wrote: > Hello: > Thanks all for your information and ideas. I like the idea of open > source; I have a fairly large (or large, by my standards anyway) > project that I am working on that is open source. > > Here's kind of what I want to prevent. I want to write a multi-player > online game; everyone will essentually end up connecting to my server > to play the game. I don't really like the idea of security through > obscurity, but I wanted to prevent a couple of problems. > 1) First I want to prevent people from hacking at the code, then using > my server as a test for their new setups. I do not want someone to > gain some extra advantage just by editing the code. > Is there some other solution to this, short of closed-source? > Thanks, > If your App meet some success, you'll need some help. You'll be able to get some only if the community grows and has access to your code. If you want to battle versus hackers, you have already lost (if your app hos no success, there will be no hacker anyway :o) ) Otherwise I guess that most online games execute all decisions and state machine transitions at server side, which is the only code you can trust. The client only forwards user inputs to the server, and display the resulting effect . JM