[TUHS] The size of EMACS, and what hides in kLOCs

Jason Stevens jsteve at superglobalmegacorp.com
Mon Feb 27 11:19:07 AEST 2017

Emacs was the central exploit that "Jagger" used to gain root access once he got his way on a box.

It's a fantastic book, with good lessons in there that still ring true, such as keeping a log, documenting what you did and why, not emailing passwords and running a honeypot.

It also showed that if you weren't in the clique you didn't get source access and that finding even part of it was a big deal.

It's a shame his next book, silicone snake oil missed the mark by so much.

On February 27, 2017 12:05:19 AM GMT+08:00, Nemo <cym224 at gmail.com> wrote:
>On 26 February 2017 at 07:46, Michael Kjörling <michael at kjorling.se>
>> On 26 Feb 2017 07:39 -0500, from jnc at mercury.lcs.mit.edu (Noel
>>> I was never happy with the size of EMACS, and it had nothing to do
>with the
>>> amount of memory resources used. That big a binary implies a very
>large amount
>>> of source, and the more lines of code, the more places for bugs...
>> But remember; without Emacs, we might never have had _The Cuckoo's
>> Egg_. Imagine the terror of that loss.
>Hhhmmm.... I must dig my copy out of storage because I do not remember
>emacs in there.
>As for emac uses, my wife was on (non-CS) staff at a local college
>affiliated with U of T.  At the time, DOS boxes sat on staff desks and
>email was via a telnet connection to an SGI box somewhere on campus.
>A BATch file connected and ran pine but shelled out to an external
>editor.  What was the editor?  Well, I saw her composing a message
>once and ending the editor session by ^X^C.

Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170227/b1b9a5e1/attachment.html>

More information about the TUHS mailing list