Path: utzoo!attcan!uunet!husc6!bloom-beacon!mit-eddie!killer!vector!nobody
From: elmo@bu-it.BU.EDU
Newsgroups: comp.dcom.telecom
Subject: Callback Security via Call-Forwarding
Message-ID: <telecom-v08i0210m03@vector.UUCP>
Date: 27 Dec 88 03:56:10 GMT
Sender: chip@vector.UUCP
Lines: 14
Approved: telecom-request@vector.uucp
X-Submissions-To: telecom@bu-cs.bu.edu
X-Administrivia-To: telecom-request@vector.uucp
X-TELECOM-Digest: volume 8, issue 210, message 3


    Bernie Cosell suggests:

    How about instead of 3-way calling you simply get "call forwarding" and
    forward all calls to your outgoing lines to some nonexistent place (maybe
    back to your incoming trunks :-).

Call-forwarding loop-prevention provides a means to break this approach.
If the hacker has a line in your central office (same machine), the
"set-up" call for call-forwarding FROM HIS line will ring through on your
already-forwarded line.

And all of this is silly if your hacker is tapping the line and listening with
his hayes in ham mode.  Encryption is the *only* way to go.