The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jsteve@superglobalmegacorp.com (Jason Stevens)
Subject: [TUHS] Harasing whistlers (Was:  UUCP mis-history?)
Date: Fri, 10 Mar 2017 08:31:36 +0800	[thread overview]
Message-ID: <777EBBB5-6B7A-43E8-82AF-8FFC26B78C72@superglobalmegacorp.com> (raw)
In-Reply-To: <alpine.BSF.2.20.1703100825520.2854@aneurin.horsfall.org>

It's not hard to whistle a handshake.  I've been able to get a modem to connect.  Of course actual data is out of the question.  It's just loud sharp tones, then just match pitch, the other modem will change a few times and just match it.

It was a silly trick whistling to modems, but these days nobody has one.  And I can't say I miss dialup.

On March 10, 2017 5:29:29 AM GMT+08:00, Dave Horsfall <dave at horsfall.org> wrote:
>On Thu, 9 Mar 2017, Noel Chiappa wrote:
>
>> Interesting: I've heard this same story, but told about TIPs and the 
>> ARPANET. A computer at BBN was set up to regularly dial all the TIP 
>> modem lines, to check that they were working. One line was always
>down, 
>> so they listened in, and heard some human say "it's just that pevert 
>> with the whistle again".
>> 
>> I wonder which one was the original: anyone know for sure?
>
>Now that takes me back; urban myth, because the calling modem didn't 
>squeak until the called modem did.
>
>-- 
>Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will
>suffer."

-- 
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/20170310/2411a275/attachment-0001.html>


      parent reply	other threads:[~2017-03-10  0:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09 15:06 Noel Chiappa
2017-03-09 16:31 ` Ron Natalie
2017-03-09 21:29 ` Dave Horsfall
2017-03-09 22:54   ` Arthur Krewat
2017-03-10  0:31   ` Jason Stevens [this message]

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=777EBBB5-6B7A-43E8-82AF-8FFC26B78C72@superglobalmegacorp.com \
    --to=jsteve@superglobalmegacorp.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).