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

Groups > comp.lang.python > #67972

Re: How security holes happen

Newsgroups comp.lang.python
Date 2014-03-06 17:53 -0800
References (5 earlier) <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>
Message-ID <e34bed3d-920b-4faa-bdef-43cf241e8cab@googlegroups.com> (permalink)
Subject Re: How security holes happen
From "Mark H. Harris" <harrismh777@gmail.com>

Show all headers | View raw

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.
   
    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