Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!hayes.fai.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: Ed_Greenberg@fin.3mail.3com.com
Newsgroups: comp.dcom.telecom
Subject: Re: Call Detail Recording
Message-ID: <11693@accuvax.nwu.edu>
Date: 4 Sep 90 15:04:00 GMT
Sender: news@accuvax.nwu.edu
Organization: TELECOM Digest
Lines: 21
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 10, Issue 618, Message 6 of 8


John Higdon tells of having an associate visit who was p*ssed that
John's SMDR recorded details of his calls.  This happened to me,
visiting a friend who has a little Panasonic switch.  Fortunately, I
was standing right by the printer and grabbed the printout.

In this case it was mild.  I'd _give_ Larry my credit card number, but
he does have kids (good kids, but kids nonetheless), and it points out
that we leave that credit card number all over the place when we dial.

On a similar subject, did you know that most Unix machines can be set
to record both bad login attempts and bad passwords entered to a good
user id?  So, if you normally log in with a password of "rosemary" and
you accidentally use "trosemary" by hitting two keys, you've left your
password for the sysadmin.  Moral: don't use the same password on more
than one system.  I forget the names of these files, but they live in
/usr/adm/something_or_other and they should most definitely be
protected 600 and owned by root.
     

Ed_Greenberg@fin.3mail.3com.com