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

Groups > comp.lang.python > #67896

Re: How security holes happen

Path csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed4a.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path <python-python-list@m.gmane.org>
X-Original-To python-list@python.org
Delivered-To python-list@mail.python.org
X-Spam-Status OK 0.009
X-Spam-Evidence '*H*': 0.98; '*S*': 0.00; 'affected': 0.07; 'granted,': 0.07; '(first': 0.09; 'debugger': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'subject:How': 0.10; 'arrived': 0.16; 'copied.': 0.16; 'marker': 0.16; 'message- id:@4ax.com': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'skipped': 0.16; 'skipping': 0.16; 'subject:security': 0.16; 'thu,': 0.19; 'command': 0.22; 'machine': 0.22; 'copied': 0.24; 'url:home': 0.24; "i've": 0.25; 'this:': 0.26; 'header:X-Complaints-To:1': 0.27; 'chris': 0.29; 'mode': 0.30; 'with,': 0.31; 'file': 0.32; 'option': 0.32; '(including': 0.33; 'raw': 0.33; 'could': 0.34; 'version': 0.36; 'disk': 0.36; 'ibm': 0.36; 'skip:> 10': 0.36; 'charset:us-ascii': 0.36; 'received:76': 0.38; 'version,': 0.38; 'to:addr:python- list': 0.38; 'bad': 0.39; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'even': 0.60; 'blank': 0.60; 'then,': 0.60; 'till': 0.61; 'new': 0.61; 'first': 0.61; 'back': 0.62; 'mar': 0.68; 'home': 0.69; 'default': 0.69; 'superior': 0.69; 'sector': 0.72; 'special': 0.74; 'differences': 0.93
X-Injected-Via-Gmane http://gmane.org/
To python-list@python.org
From Dennis Lee Bieber <wlfraed@ix.netcom.com>
Subject Re: How security holes happen
Date Wed, 05 Mar 2014 19:24:52 -0500
Organization IISS Elusive Unicorn
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>
Mime-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Transfer-Encoding 7bit
X-Gmane-NNTP-Posting-Host adsl-76-249-29-56.dsl.klmzmi.sbcglobal.net
X-Newsreader Forte Agent 6.00/32.1186
X-No-Archive YES
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.7850.1394065503.18130.python-list@python.org> (permalink)
Lines 35
NNTP-Posting-Host 2001:888:2000:d::a6
X-Trace 1394065503 news.xs4all.nl 2830 [2001:888:2000:d::a6]:57243
X-Complaints-To abuse@xs4all.nl
Xref csiph.com comp.lang.python:67896

Show key headers only | View raw

On Thu, 6 Mar 2014 02:16:53 +1100, Chris Angelico <rosuav@gmail.com>
declaimed the following:


>My first IBM machine (first I used - the first computer I actually
>personally *owned* wasn't till this century) was an Epson
>XT-compatible. We had GW-BASIC and Q-BASIC, and a much superior form
>of DEBUG.EXE that came with, get this, an inbuilt mini-assembler! Yes,
>I could do this:
>

	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.

	The LS-DOS debugger had a mode where it could do raw sector I/O
(including the special marker used for the directory). I did differences on
the prior OS version and the update version, skipping the bad sector. From
this, I found the main change in the affected file was the default option
for the directory command -- so I used debugger to copy the update to a
blank disk, skipping the bad sector; then used the prior version and copied
just the skipped sector to the new disk.

	That actually produced a working "update" system disk, which I used
while sending the bad disk back to LSI for replacement.


	Granted, the only OTHER debugger I've ever used is the one from
VAX/VMS.
-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
    wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

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