Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #67706

Re: How security holes happen

Path csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!newsfeed.xs4all.nl!newsfeed1a.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path <rosuav@gmail.com>
X-Original-To python-list@python.org
Delivered-To python-list@mail.python.org
X-Spam-Status OK 0.000
X-Spam-Evidence '*H*': 1.00; '*S*': 0.00; 'python.': 0.02; 'interpreter': 0.05; 'that?': 0.05; 'subject:How': 0.10; 'url:blog': 0.10; 'cc:addr:python-list': 0.11; 'python': 0.11; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'lisp': 0.16; 'lisp,': 0.16; 'merely': 0.16; 'subject:security': 0.16; 'url:post': 0.16; 'utc,': 0.16; 'do,': 0.16; 'wrote:': 0.18; 'wed,': 0.18; 'cc:addr:python.org': 0.22; 'simpler': 0.24; 'cc:2**0': 0.24; 'header:In-Reply-To:1': 0.27; 'chris': 0.29; 'am,': 0.29; 'message-id:@mail.gmail.com': 0.30; 'that.': 0.31; 'monday,': 0.33; 'done.': 0.35; 'received:google.com': 0.35; 'march': 0.61; 'mar': 0.68; 'video...': 0.84; 'to:none': 0.92
DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=ut3A9dkdcen+gX47Ng5PtMN84wyASqpi+C+D0l9f7O8=; b=vXaQ3NQe8a4AxubYqnyhXkQl8tiQHpxxr5ZWyRbnBKYLvN+BBnxO71AQ1zxyoSczej gW0sfWzGoDzLNzv2Re/BayhSHAkd6xmaIeoy5/aEkFI9rkjJkEouo46g+h2kA7ynk0NX P6fNykjvpBL1rBQghWRkuAvSWIg4Psl3P3TeeBzWlOM23p9tE4Dy8398ImY1EwWKW2o0 5TUbDh3+dxYStPEMRDo3k3vKKl6OHEthP+KWwGxzwP8m3nSXDecRjijZs6Iwk5YlwTTx nmNtUzDGIVJGJeBBo/+al5jgV66B5df/enmZm7sXL9c0J6yO0qOp0Ao5YJcJaDM8RbxW JlRQ==
MIME-Version 1.0
X-Received by 10.66.118.71 with SMTP id kk7mr884440pab.14.1393952864474; Tue, 04 Mar 2014 09:07:44 -0800 (PST)
In-Reply-To <99ca7396-bcb8-49f9-b486-56ae88aa00e5@googlegroups.com>
References <lf22t1$sgh$1@ger.gmane.org> <20140303221926.GA57537@cskk.homeip.net> <CAPTjJmpk+5hRUS7Xp1C73Hypc5qhm4HXZwMTJOdqfx_8JjfKSA@mail.gmail.com> <mailman.7678.1393887688.18130.python-list@python.org> <99ca7396-bcb8-49f9-b486-56ae88aa00e5@googlegroups.com>
Date Wed, 5 Mar 2014 04:07:44 +1100
Subject Re: How security holes happen
From Chris Angelico <rosuav@gmail.com>
Cc "python-list@python.org" <python-list@python.org>
Content-Type text/plain; charset=UTF-8
X-BeenThere python-list@python.org
X-Mailman-Version 2.1.15
Precedence list
List-Id General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe <https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive <http://mail.python.org/pipermail/python-list/>
List-Post <mailto:python-list@python.org>
List-Help <mailto:python-list-request@python.org?subject=help>
List-Subscribe <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups comp.lang.python
Message-ID <mailman.7731.1393952868.18130.python-list@python.org> (permalink)
Lines 9
NNTP-Posting-Host 2001:888:2000:d::a6
X-Trace 1393952868 news.xs4all.nl 2873 [2001:888:2000:d::a6]:50247
X-Complaints-To abuse@xs4all.nl
Xref csiph.com comp.lang.python:67706

Show key headers only | View raw

On Wed, Mar 5, 2014 at 3:41 AM,  <sffjunkie@gmail.com> wrote:
> On Monday, 3 March 2014 22:55:32 UTC, Chris Kaynor  wrote:
>> You can go much simpler than that. Merely port Python to LISP, then write a LISP interpreter in Python. Done.
>
> http://blog.pault.ag/post/46982895940/heres-my-talk-from-pycon-2013-i-tried-to-queue

I don't have time to watch an hour-long video... what'd he do, exactly that?

ChrisA

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Re: How security holes happen Chris Kaynor <ckaynor@zindagigames.com> - 2014-03-03 14:55 -0800
  Re: How security holes happen sffjunkie@gmail.com - 2014-03-04 08:41 -0800
    Re: How security holes happen Chris Angelico <rosuav@gmail.com> - 2014-03-05 04:07 +1100
    Re: How security holes happen Skip Montanaro <skip@pobox.com> - 2014-03-04 11:16 -0600
    Re: How security holes happen Ned Batchelder <ned@nedbatchelder.com> - 2014-03-04 15:47 -0500
    Re: How security holes happen Ethan Furman <ethan@stoneleaf.us> - 2014-03-04 13:49 -0800
      Re: How security holes happen Marko Rauhamaa <marko@pacujo.net> - 2014-03-05 00:48 +0200
        Re: How security holes happen Chris Angelico <rosuav@gmail.com> - 2014-03-05 09:57 +1100
          Re: How security holes happen Roy Smith <roy@panix.com> - 2014-03-04 17:59 -0500
            Re: How security holes happen Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-03-04 23:16 +0000
            Re: How security holes happen Chris Angelico <rosuav@gmail.com> - 2014-03-05 10:22 +1100
            Re: How security holes happen Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-03-04 23:40 +0000
        Re: How security holes happen Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-03-04 19:31 -0500
        Re: How security holes happen Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-03-04 19:30 -0500
          Re: How security holes happen Roy Smith <roy@panix.com> - 2014-03-04 20:57 -0500
            Re: How security holes happen MRAB <python@mrabarnett.plus.com> - 2014-03-05 04:11 +0000
              Re: How security holes happen Marko Rauhamaa <marko@pacujo.net> - 2014-03-05 08:37 +0200
                Re: How security holes happen Steven D'Aprano <steve@pearwood.info> - 2014-03-05 08:26 +0000
                Re: How security holes happen Ben Finney <ben+python@benfinney.id.au> - 2014-03-05 19:57 +1100
                Re: How security holes happen Marko Rauhamaa <marko@pacujo.net> - 2014-03-05 11:01 +0200
                Re: How security holes happen "Mark H. Harris" <harrismh777@gmail.com> - 2014-03-05 06:11 -0800
                Re: How security holes happen Chris Angelico <rosuav@gmail.com> - 2014-03-06 02:16 +1100
                Re: How security holes happen Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-03-05 19:24 -0500
                Re: How security holes happen "Mark H. Harris" <harrismh777@gmail.com> - 2014-03-05 17:24 -0800
                Re: How security holes happen MRAB <python@mrabarnett.plus.com> - 2014-03-06 01:40 +0000
                Re: How security holes happen "Mark H. Harris" <harrismh777@gmail.com> - 2014-03-05 18:07 -0800
                Re: How security holes happen Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-03-06 19:28 -0500
                Re: How security holes happen "Mark H. Harris" <harrismh777@gmail.com> - 2014-03-06 17:53 -0800
                Re: How security holes happen MRAB <python@mrabarnett.plus.com> - 2014-03-07 02:13 +0000
                Re: How security holes happen "Mark H. Harris" <harrismh777@gmail.com> - 2014-03-06 18:39 -0800
                Re: How security holes happen Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-03-07 19:46 -0500
                Re: How security holes happen Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-03-07 19:43 -0500
        Re: How security holes happen Neil Cerutti <neilc@norwich.edu> - 2014-03-05 14:19 +0000
          Re: How security holes happen Marko Rauhamaa <marko@pacujo.net> - 2014-03-05 16:54 +0200
            Re: How security holes happen Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-03-05 18:42 +0000
              Re: How security holes happen Chris Angelico <rosuav@gmail.com> - 2014-03-06 06:00 +1100
        Re: How security holes happen Grant Edwards <invalid@invalid.invalid> - 2014-03-05 15:28 +0000
        Re: How security holes happen Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-03-05 15:47 +0000
          Re: How security holes happen "Mark H. Harris" <harrismh777@gmail.com> - 2014-03-05 08:37 -0800

csiph-web