The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: doug@cs.dartmouth.edu (Doug McIlroy)
Subject: [TUHS] Origin of the MOTD file?
Date: Thu, 15 Mar 2018 16:00:10 -0400	[thread overview]
Message-ID: <201803152000.w2FK0Aul031777@coolidge.cs.Dartmouth.EDU> (raw)


> So what are its origins? Where did it first appear?

It was a direct copy from CTSS, which already had it
n 1965 when we BTL folk began to use it.

The greatest MOTD story of all time happened at CTSS.

To set the stage, the CTSS editor made a temp file,
always of the same name, in one's home directory.
The MOTD was posted by the administrator account.

The password file was plain text, maintained by
editing it.

And multiple people had access to the administrator
account.

It happened one day that one administrator was
working on the password file at the same time
another was posting MOTD. The result: the password
file (probably the most secret file on the system)
got posted as the MOTD (the most public).

Upon seeing the password file type out before him,
an alert user shut the machine down by writing
and running one line of assembly code:

	HERE	TRA *HERE

(The star is for indirect addressing, and indirection
was transitive.)

Doug


             reply	other threads:[~2018-03-15 20:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 20:00 Doug McIlroy [this message]
2018-03-15 20:51 ` Dave Horsfall
  -- strict thread matches above, loose matches on Subject: below --
2018-03-15 15:29 Dan Cross
2018-03-15 15:35 ` Ron Natalie
2018-03-15 15:36   ` Chet Ramey
2018-03-15 15:41     ` Ron Natalie
2018-03-15 20:20     ` Dave Horsfall
2018-03-15 20:25       ` Warner Losh
2018-03-15 15:51 ` Clem Cole
2018-03-15 15:53   ` Clem Cole
2018-03-15 16:55   ` Ron Natalie
2018-03-15 18:04 ` Jeremy C. Reed

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=201803152000.w2FK0Aul031777@coolidge.cs.Dartmouth.EDU \
    --to=doug@cs.dartmouth.edu \
    /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).