Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!bu.edu!telecom-request
From: russell@spdcc.com (Tim Russell)
Newsgroups: comp.dcom.telecom
Subject: Re: Dr. Stoll's Secure Phone Calls
Message-ID: <72183@bu.edu.bu.edu>
Date: 13 Jan 91 03:07:26 GMT
Sender: news@bu.edu.bu.edu
Organization: S.P. Dyer Computer Consulting, Cambridge MA
Lines: 26
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 11, Issue 32, Message 5 of 7


In article <72160@bu.edu.bu.edu> roeber@cithe1.cithep.caltech.edu
(Frederick Roeber) writes:

>A friend of mine, who does military security work, said this is the
>result of calling a non-secure phone from the government's secure
>phone system and trying to initiate a secure call.  When making a
>secure call on this system, one first makes an ordinary phone call --
>over any network, FTS, AT&T, or whoever.  When the other end has been
>reached, one presses the `secure' button.

    Quite true - my brother works as an engineer for a government
contract company in Dallas that produces a new phone switch used,
among other places, at Cheyenne Mountain.

    He was telling me that their system has this feature, where
someone who calls in first hears a computer-played "Go secure"
repeated over and over, then once they do that, connects them with
their party.

    Anyway, the thing that's neat is that the message is his voice
digitized, so his voice will be heard if/when "the big one" comes.



Tim Russell   Omaha NE   russell@spdcc.com