From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] History of exploits - request for authors
Date: Tue, 19 Dec 2017 12:08:21 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.1712191158340.92288@aneurin.horsfall.org> (raw)
In-Reply-To: <8460DBBB-A4E2-468B-B294-A2B021213F3C@alchemistowl.org>
On Mon, 18 Dec 2017, Arrigo Triulzi wrote:
[...]
> 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.
Depends on exactly what you want; I don't have time to document my, err,
past before your deadline, but my favourites under Edition 6 would be:
Planting 0 into u.u_uid via the switch register (physical access reqd).
Planting same, but by sending a negative signal to yourself.
And the usual run of insecure directory permissions etc.
Planting trojans such as "pwd" called with 17 args (and same size!).
Leaving a "login" simulator on a terminal (quite common).
And on KRONOS, you could get system privileges quite easily on a terminal.
With OS/360, you dumped low memory and traced where "SVC 254" went.
Is that the sort of stuff you're after?
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
next prev parent reply other threads:[~2017-12-19 1:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 10:31 Arrigo Triulzi
2017-12-19 1:08 ` Dave Horsfall [this message]
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=alpine.BSF.2.21.1712191158340.92288@aneurin.horsfall.org \
--to=dave@horsfall.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).