🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.dcom.sys.cisco
Article #1938

Don't trust Caller-ID for security

#1938
From: Kevin Kadow
Date: Tue, 23 Jan 1996 20:21
21 lines
1398 bytes
In article <4dr6nr$1qm@raid.omnilink.net>,
Hannes Deeken <hd@omnilink.net> wrote:
>Bill Miskovetz <misko@cisco.com> writes:
>>Usually indicates that your switch either is not delivering calling line
>>id, or if it is, it is delivering a number different from that which you
>>have configured on your dialer map statement.  If calling line id is
>>being delivered, use the 'name <cli #>' option to the dialer map.  If
>>it is not being delivered, use ppp authentication.
>
>Is this feature ('name <cli #>') documented somewhere on UniverCD?


WARNING:

The calling line id information (at least in the USA) is NOT trustworthy, and
should not be used as the sole means of authentication.

Due to a bug in DMS-100 switches, a malicious person with a PRI circuit
provisioned from a true DMS-100 can set any valid directory number on their
ISDN device, and the nationwide telephone network will deliver it as a valid
calling line ID number.
Technical Details
Message-ID: <4e3g0n$a1j@newdelph.cig.mot.com>
Path: arc1-ca.pugleaf.net!newdelph.rtsg.mot.com!komondor!kadow
References: <821786749.22894@news.Colorado.EDU> <4dr6nr$1qm@raid.omnilink.net>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!newdelph.rtsg.mot.com!komondor!kadow
From: kadow@komondor.cig.mot.com (Kevin Kadow)
Newsgroups: comp.dcom.sys.cisco,comp.dcom.isdn
Subject: Don't trust Caller-ID for security
Date: 23 Jan 1996 20:21:43 GMT
Organization: Motorola Cellular Infrastructure Group
Message-ID: <4e3g0n$a1j@newdelph.cig.mot.com>
References: <821786749.22894@news.Colorado.EDU> <4dr6nr$1qm@raid.omnilink.net>
NNTP-Posting-Host: komondor.cig.mot.com