home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!rutgers!faatcrl!jprad
- From: jprad@faatcrl.UUCP (Jack Radigan)
- Newsgroups: comp.sys.amiga.datacomm
- Subject: Re: JRCOMM Crash
- Message-ID: <3392@faatcrl.UUCP>
- Date: 23 Jul 92 13:59:06 GMT
- References: <Ray_Hines.7589@dream.uucp> <1992Jul13.214026.8272@ninja.zso.dec.com> <1992Jul16.175759.841@TorreyPinesCA.ncr.com> <CONSP03.92Jul17231553@bingsunb.cc.binghamton.edu> <3373@faatcrl.UUCP> <CONSP03.92Jul23010742@bingsunb.cc.binghamton.edu>
- Organization: FAA Technical Center, Atlantic City NJ
- Lines: 31
-
- consp03@bingsuns.cc.binghamton.edu (Kriston J. Rehberg) writes:
-
- >> Interesting, as the BBS has no account with your name...
-
- >I called it once about 6 months ago...
-
- The user file stands at about 2500 users, no accounts are *ever* deleted and
- the file was created more than a year ago.
-
- You're not in there.
-
- >> If you don't give a shit, why bother commenting about it?
-
- >Because I had the time (hehe).
- >JRComm is still a good program, however I think a bit more (or even
- >less) work should have gone into the protection mechanism.
-
- To date, one person has sent in the copy of JR-Comm that he was using and
- the .def file that went along with it. The .def file was corrupted and caused
- the hack message to appear.
-
- Other than that, the few complaints that I did get about this message have
- never been followed up with sending me the executable and .def file that they
- were using.
-
- The mechanism is a bit sneaky to be sure, but it is not that complex and
- as much as you think otherwise, solid. The fact that no one, bar one person,
- has sent me copies of what they were using tells me that they are using a
- hacked version of the program.
-
- -jack-
-