The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: ARPANET Information Brochure (December 1985)
Date: Mon, 16 Oct 2017 12:09:50 -0400	[thread overview]
Message-ID: <CAC20D2Or1oNQuNmDE4HuoJDt_nOa61fu3NwaNZ112NNod3UQvA@mail.gmail.com> (raw)
In-Reply-To: <BEF011B5-4F7C-407D-99D4-C38998CC7385@gmail.com>

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

Don't forget the cost of the IMP itself was just the beginning.  The fees
to 'TPC' for the 1/2 duplex 9600 serial lines in those days were very, very
expensive.   DARPA paid for them for each site in a large deal it had with
AT&T.    I don't remember where I saw it, but what sticks out in my mind
for those days was that cost of a site (host) on the ARPAnet was approx
$125K / year per host in an ARPA grant.

Which really explains 'security.' In practice nobody was going to risk
letting just anyone hack their system so much that it put the site at
risk.   Truth is we did not try to break in because we all had access, but
if it you needed a $.5-2M PDP-10 to connect to the internet, a free IMP
slot (each IMP supplied 4) and the leases on the wires.  So it was just not
practical to think like we do today, much less act that way.

It was not so much security by obscurity, as security by practical
economics.  Moore's law, Ethernet and cheap processing power is what blow
that up.

On Mon, Oct 16, 2017 at 11:38 AM, Don Hopkins <don at donhopkins.com> wrote:

> https://www.youtube.com/watch?v=hVth6T3gMa0
>
>
> I love the way that geeky guy smugly rubs his hands together, leans back
> and chuckles when he say “We have our very own IMP. (Huh, huh huh, sigh.)”
>
> I would totally chuckle that way if I had my own IMP.
>
> -Don
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171016/b545f174/attachment.html>


  reply	other threads:[~2017-10-16 16:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 15:09 Michael-John Turner
2017-10-16 15:35 ` Don Hopkins
2017-10-16 15:38   ` Don Hopkins
2017-10-16 16:09     ` Clem Cole [this message]
2017-10-16 16:44       ` Don Hopkins
2017-10-17  0:34         ` Grant Taylor
2017-10-17 18:33     ` Ron Natalie
2017-10-17  0:27 ` Larry McVoy
2017-10-17  0:44 Noel Chiappa
2017-10-17  2:00 ` Larry McVoy
2017-10-17 12:57 Noel Chiappa
2017-10-17 14:32 ` Larry McVoy
2017-10-17 13:01 Noel Chiappa

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=CAC20D2Or1oNQuNmDE4HuoJDt_nOa61fu3NwaNZ112NNod3UQvA@mail.gmail.com \
    --to=clemc@ccc.com \
    /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).