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

Groups > comp.lang.python > #67906

Re: How security holes happen

Path csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!eternal-september.org!feeder.eternal-september.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed1.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.020
X-Spam-Evidence '*H*': 0.96; '*S*': 0.00; 'wang': 0.07; 'wednesday,': 0.07; 'bytes.': 0.09; 'cambridge': 0.09; 'subject:How': 0.10; '6502': 0.16; 'arrived': 0.16; 'chip': 0.16; 'copied.': 0.16; 'from:addr:mrabarnett.plus.com': 0.16; 'from:addr:python': 0.16; 'from:name:mrab': 0.16; 'intel,': 0.16; 'it;': 0.16; 'message- id:@mrabarnett.plus.com': 0.16; 'motorola': 0.16; 'received:192.168.1.4': 0.16; 'subject:security': 0.16; "up'": 0.16; 'folks': 0.16; 'language': 0.16; 'wrote:': 0.18; '(not': 0.18; 'machine': 0.22; 'memory': 0.22; 'platforms': 0.22; 'programming': 0.22; 'coding': 0.22; 'header:User-Agent:1': 0.23; 'loved': 0.24; 'processor': 0.24; 'gets': 0.27; 'header:In-Reply- To:1': 0.27; 'dos': 0.30; 'purchased': 0.30; 'technology.': 0.30; 'code': 0.31; 'fast.': 0.31; 'anyone': 0.31; 'front': 0.32; 'could': 0.34; 'basic': 0.35; 'but': 0.35; 'disk': 0.36; 'ram': 0.36; 'so,': 0.37; 'to:addr:python-list': 0.38; 'bad': 0.39; 'to:addr:python.org': 0.39; 'even': 0.60; 'temporarily': 0.60; 'then,': 0.60; 'march': 0.61; 'simple': 0.61; 'first': 0.61; 'real': 0.63; 'personal': 0.63; 'today': 0.64; 'great': 0.65; 'capable': 0.67; 'realized': 0.68; 'home': 0.69; 'integrated': 0.69; 'sector': 0.72; 'saw': 0.77; 'grew': 0.84; 'instantly': 0.84; 'processor.': 0.84; 'was...': 0.84; 'sectors,': 0.91
X-CM-Score 0.00
X-CNFS-Analysis v=2.1 cv=eZmzft0H 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=29sdinL9AAAA:8 a=fvn0VSkRbZ884B5XgtEA:9 a=chnsrMkpCq5sxlAK:21 a=afoAvvnDbWamu4i9:21 a=QEXdDO2ut3YA:10 a=t2Tkznx58bIA:10 a=11lS6zLlWp0A:10
X-AUTH mrabarnett:2500
Date Thu, 06 Mar 2014 01:40:05 +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.7759.1393972610.18130.python-list@python.org> <87d2i1mvg7.fsf@elektro.pacujo.net> <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>
In-Reply-To <5adebc12-aa37-4139-82d8-563f46a27dc0@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.7856.1394070008.18130.python-list@python.org> (permalink)
Lines 45
NNTP-Posting-Host 2001:888:2000:d::a6
X-Trace 1394070008 news.xs4all.nl 2924 [2001:888:2000:d::a6]:41812
X-Complaints-To abuse@xs4all.nl
Xref csiph.com comp.lang.python:67906

Show key headers only | View raw

On 2014-03-06 01:24, Mark H. Harris wrote:
> On Wednesday, March 5, 2014 6:24:52 PM UTC-6, Dennis Lee Bieber
> wrote:
>> I must have had a deprived life...
>>
>> The only "debug" on a home system I ever used was the one in
>> LS-DOS. And even then, it was only because an OS update disk
>> arrived with a bad sector and could not be copied.
>
> Not many people realized what they had in front of them. The only
> reason you might is if you 'grew up' on a system that required
> machine coding;  like the Wang 700 series, or the MITS Altair 8800,
> or the VIC 20 with VicMon.
>
> I grew up with all three. So, before I ever learned a line of BASIC I
> was coding machine language (not assembler) on the three platforms
> above... the wang used integrated circuits, but had to processor
> chip;  the MITS used the very first 8080 chip from Intel, and the VIC
> 20 used the 6502 from Motorola.
>
The 6502 came from MOS Technology. Motorola made the 6800.

> My first personal computer (I did not own it, it was temporarily
> loaned to me) was the VIC 20.  It only had 5k of memory, so anyone
> who did any real programming on it purchased the VicMon cartridge
> which was a 'machine language monitor'. It was "DEBUG.COM" for the
> VIC 20.
>
5K? Luxury! I started with the Science of Cambridge Mk14. Including the
RAM on the I/O chip, it had 640 bytes.

> When I got the first copy of DOS on floppy and saw DEBUG.COM I knew
> instantly what it was... a machine language monitor system for
> reading and writing machine code (8086 / 8088) in memory, or to disk
>  sectors, or to disk as a file-name.  It wasn't just a
> debugger---hardly! It was (and still is, yes, I still use it) a
> simple clean full-blown machine language monitor capable today just
> as then, to build sophisticated applications with 1's and 0's/
>
> It was also my cup of tea, as it were.  The folks who used the MITS
> Altair 8800 hated punching code in by hand; gets old fast.  But not
> for me. I loved it, because I was as interested in the 8080 processor
> as I was in writing programs for it; it was great fun experimenting
> with memory and the processor.
>

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