Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: John Bokma Newsgroups: comp.lang.python Subject: Re: obviscating python code for distribution Date: Wed, 18 May 2011 12:31:58 -0500 Organization: Castle Amber Lines: 27 Message-ID: <87mxijzzht.fsf@castleamber.com> References: <4DD08620.4030507@tysdomain.com> <5h9ca8-ekq.ln1@svn.schaathun.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: individual.net fq/q0w2sapipXpTRYpyHFA1X8yOezsTLQgw5jHr0XtdaFI/6+w Cancel-Lock: sha1:e2f/iBSNHYjLIuSi8OJj07XHtd0= sha1:RHqbxNiXLF5Gh8sJJe6yM+grm7s= X-Url: http://johnbokma.com/ User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:5711 Chris Angelico writes: > On Thu, May 19, 2011 at 2:54 AM, geremy condra wrote: >> On Wed, May 18, 2011 at 12:36 AM, Hans Georg Schaathun wrote: >>> But then, nothing is secure in any absolute sense. >> >> If you're talking security and not philosophy, there is such a thing >> as a secure system. As a developer you should aim for it. > > Agreed. Things can be secure if you accept caveats. A good server > might be secure as long as attackers cannot, say: > * Get physical access to the server, remove the hard disk, and tamper with it > * Hold a gun to the developer and say "Log me in as root or you die" > * Trigger a burst of cosmic rays that toggle some bits in memory You forgot the most important one: * if none of the software running on it has exploitable issues Personally, I think it's best to understand that no server is ever secure and hence one must always be prepared that a breach can happen. -- John Bokma j3b Blog: http://johnbokma.com/ Perl Consultancy: http://castleamber.com/ Perl for books: http://johnbokma.com/perl/help-in-exchange-for-books.html