Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #67896
| From | Dennis Lee Bieber <wlfraed@ix.netcom.com> |
|---|---|
| Subject | Re: How security holes happen |
| Date | 2014-03-05 19:24 -0500 |
| Organization | IISS Elusive Unicorn |
| References | (4 earlier) <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> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.7850.1394065503.18130.python-list@python.org> (permalink) |
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
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