Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!emory!ogicse!zephyr.ens.tek.com!gvgpsa!gold.gvg.tek.com!shaunc
From: shaunc@gold.gvg.tek.com (Shaun Case)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Warning for ProComm Users
Keywords: SECURITY, PUBLIC EMBARRASSMENT
Message-ID: <2197@gold.gvg.tek.com>
Date: 19 Apr 91 19:54:49 GMT
References: <1991Apr12.002356.24990@comp.vuw.ac.nz> <1991Apr16.010424.22198@brainiac.mn.org> <1991Apr19.030846.24013@bronze.ucs.indiana.edu>
Organization: Grass Valley Group, Grass Valley, CA
Lines: 30

In article <1991Apr19.030846.24013@bronze.ucs.indiana.edu> rschmidt@copper.ucs.indiana.edu (roy schmidt) writes:
>This is ridiculous!  Chris McDonald by now must be regretting that
>he/she posted such a dumb note.

I don't think it was dumb.

>1.  For security purposes, any of you folks in the DoD who are reading
>this should remember the series that has ensued as a lesson.  Any time
>you discover what may be a security problem, don't advertise your
>problem to the world (note that even Timo Salmi of Finland responded at
>one point.)  Call your security people, and let them take care of it.
>If you feel you *must* send out something or bust, then compose a memo
>for local consumption, and then eat it and call your security people!

I disagree completely.  The free flow of information should NEVER be
impeded, _especially_ not by the US military.  Are you trying to tell
me that a feature of Procomm (arguably the worst PC term program next
to Bitcom) is a national security issue?  Give me a break.

>2.  Why continue speculating on this problem?  Let's drop this whole
>thing and move back to the business for which this group was formed:
>squandering government money!  :-)

Ah, my 30% taxes at work.  I do prefer this to a number of alternatives. :)

>Roy Schmidt, Capt, USAF (Retired)
>Former security-obsessed officer

Shaun Case, hacker (unretired)
Current anti-security-obsessed taxpayer