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

Groups > comp.lang.python > #67976

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!newsfeed3a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path <python@mrabarnett.plus.com>
X-Original-To python-list@python.org
Delivered-To python-list@mail.python.org
X-Spam-Status OK 0.006
X-Spam-Evidence '*H*': 0.99; '*S*': 0.00; 'intel': 0.07; 'subject:How': 0.10; 'wrote': 0.14; '6502': 0.16; 'chip': 0.16; 'from:addr:mrabarnett.plus.com': 0.16; 'from:addr:python': 0.16; 'from:name:mrab': 0.16; 'message-id:@mrabarnett.plus.com': 0.16; 'motorola': 0.16; 'quite.': 0.16; 'received:192.168.1.4': 0.16; 'received:84.93': 0.16; 'received:84.93.230': 0.16; 'subject:security': 0.16; 'z80': 0.16; 'thursday,': 0.16; 'wrote:': 0.18; 'header:User-Agent:1': 0.23; 'header:In-Reply- To:1': 0.27; 'rest': 0.29; 'instruction': 0.29; 'moved': 0.30; '(although': 0.31; 'with,': 0.31; 'compatible': 0.32; 'received:84': 0.35; 'but': 0.35; 'bought': 0.36; 'architecture': 0.38; 'to:addr:python-list': 0.38; 'to:addr:python.org': 0.39; 'even': 0.60; 'march': 0.61; 'details.': 0.61; 'here:': 0.62; 'back': 0.62; 'etc,': 0.84
X-CM-Score 0.00
X-CNFS-Analysis v=2.1 cv=JLW1sq6b c=1 sm=1 tr=0 a=0nF1XD0wxitMEM03M9B4ZQ==:117 a=0nF1XD0wxitMEM03M9B4ZQ==:17 a=0Bzu9jTXAAAA:8 a=sASEtNAQL0YA:10 a=ihvODaAuJD4A:10 a=IkcTkHD0fZMA:10 a=EBOSESyhAAAA:8 a=AgydtYVrLA358Ka4ar0A:9 a=QEXdDO2ut3YA:10
X-AUTH mrabarnett:2500
Date Fri, 07 Mar 2014 02:13:02 +0000
From MRAB <python@mrabarnett.plus.com>
User-Agent Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version 1.0
To python-list@python.org
Subject Re: How security holes happen
References <mailman.7777.1393980007.18130.python-list@python.org> <roy-4E7DBB.20574304032014@news.panix.com> <mailman.7789.1393992721.18130.python-list@python.org> <871tyhp2vd.fsf@elektro.pacujo.net> <5316dfa4$0$2923$c3e8da3$76491128@news.astraweb.com> <d83922b0-2969-4fa1-aa3a-075f7ad4c44a@googlegroups.com> <CAPTjJmpCiNC7HHSQwmD4piTQt2VJY4mjQVSMvH=uCVqywm8ifQ@mail.gmail.com> <mailman.7850.1394065503.18130.python-list@python.org> <5adebc12-aa37-4139-82d8-563f46a27dc0@googlegroups.com> <mailman.7885.1394152206.18130.python-list@python.org> <e34bed3d-920b-4faa-bdef-43cf241e8cab@googlegroups.com>
In-Reply-To <e34bed3d-920b-4faa-bdef-43cf241e8cab@googlegroups.com>
Content-Type text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding 7bit
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.7887.1394158390.18130.python-list@python.org> (permalink)
Lines 22
NNTP-Posting-Host 2001:888:2000:d::a6
X-Trace 1394158390 news.xs4all.nl 2874 [2001:888:2000:d::a6]:49363
X-Complaints-To abuse@xs4all.nl
Xref csiph.com comp.lang.python:67976

Show key headers only | View raw

On 2014-03-07 01:53, Mark H. Harris wrote:
> On Thursday, March 6, 2014 6:28:58 PM UTC-6, Dennis Lee Bieber wrote:
>>
>> 	The 6502 was NOT a Motorola chip (they had the 6800).  The 6502 was MOS
>
> That's funny... did you not see what I wrote back to MRAB?   Here:
>
> The MOS 6502 is to the Motorola 6800 what the Zilog Z80 was to the Intel 8080.
>
Not quite.

The Z80's architecture and instruction set is a superset of that of the
8080; the 6502's architecture and instruction set isn't a superset of,
or even compatible with, that of the 6800 (although it can use the same
I/O, etc, chips).

>      The same engineers who designed the 6800 moved out and then designed
> the 6502; actually ended up in a law suit of sorts--- but I don't remember the
> details. Anyway, the 6502 was bought outright by Commodore, and the rest
> is history with the VIC20.
>

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