The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arrigo@alchemistowl.org (Arrigo Triulzi)
Subject: [TUHS] History of exploits - request for authors
Date: Mon, 18 Dec 2017 11:31:40 +0100	[thread overview]
Message-ID: <8460DBBB-A4E2-468B-B294-A2B021213F3C@alchemistowl.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]

Dear all,

I am starting a new “history” section of the “weird machines and security” publication PoC||GTFO (https://www.alchemistowl.org/pocorgtfo for my mirror, https://www.nostarch.com/gtfo for a printed compilation of the first 15 issues).

Ideally we would like some articles about the history of security exploits where the historical importance is emphasised: we always get authors willing to tell us about the latest and greatest web exploit but they often lack any historical perspective about what has been done before.

As PoC||GTFO has a strong emphasis on weird machines and generally forgotten hardware and software I thought that the contributors to TUHS would be ideally placed to write something about their preferred security exploits in the past. I have fond memories of taking over a machine using and NFS /home filesystem exported to the wide-world, of someone trying to hack into my MasPar via the DEC Ultrix which controlled it, etc. but I am really rather interested in other perspectives.

I hope a few of you will want to contribute something to the collection, there is still space for the January 2018 edition if anyone is so inclined.

Cheers,

Arrigo



             reply	other threads:[~2017-12-18 10:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18 10:31 Arrigo Triulzi [this message]
2017-12-19  1:08 ` Dave Horsfall
2017-12-19 20:17   ` Derek Fawcus
2017-12-19 20:32     ` Ron Natalie
2017-12-20  2:22       ` Dave Horsfall
2017-12-19 23:45     ` Dave Horsfall
2017-12-29 11:22     ` Arrigo Triulzi
2017-12-19 20:25   ` Derek Fawcus
2017-12-19  1:25 ` Larry McVoy
2017-12-20  0:01   ` Nemo
2017-12-29 11:14   ` Arrigo Triulzi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8460DBBB-A4E2-468B-B294-A2B021213F3C@alchemistowl.org \
    --to=arrigo@alchemistowl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).