Path: utzoo!telecom-request Date: Thu, 9 May 91 02:42 GMT From: "Sander J. Rabinowitz" <0003829147@mcimail.com> Newsgroups: comp.dcom.telecom Subject: AT&T's Call Manager: Security Problem? Message-ID: Organization: TELECOM Digest Sender: Telecom@eecs.nwu.edu 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 351, Message 1 of 10 Lines: 29 On May 5th, I wrote the Moderator to ask him to clarify AT&T's Call Manager for me. Here's what he wrote: > [Moderator's Note: When I used it here (0 + NPA + 7D - pause for tone > - enter 15xx), the call was processed, and the billing came to my line > the following month with notations on the bill entitled 'account code > xx', where 'xx' was the two digits I had entered after the '15' when > making the call. It appears nothing further is required to use this > service. PAT] First of all, I think it's good that AT&T is doing this, and I plan to use the service myself. Having said that, however ... isn't there a security problem that arises whenever 15xx can be substituted for a valid calling card number? I would hope AT&T has a way of blocking this particular service for people who so request it ... indeed, it would seem blocking would become mandatory in certain situations (ie., public telephones, COCOTS). Sander J. Rabinowitz | sjr@mcimail.com -or- | +1 615 661 4645 Brentwood, Tennessee | sander@attmail.com | | The usual disclaimers apply. [Moderator's Note: I beleive it is blocked from payphones, but I don't know about COCOTS. It would be interesting to find out how it responds to 10288 plus calling from a COCOT. PAT]