home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Path: sparky!uunet!usc!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!eagle!tedwright.lerc.nasa.gov!wright
- From: wright@lims01.lerc.nasa.gov (Ted Wright)
- Subject: Re: PC/TCP 2.1 copy protection
- Message-ID: <wright.32.0@lims01.lerc.nasa.gov>
- Sender: news@eagle.lerc.nasa.gov
- Nntp-Posting-Host: tedwright.lerc.nasa.gov
- Organization: NASA Lewis Research Center
- References: <1992Sep8.214208.41914@clinicom.com>
- Distribution: usa
- Date: Thu, 10 Sep 1992 13:09:31 GMT
- Lines: 18
-
- In article <1992Sep8.214208.41914@clinicom.com> john@clinicom.com (John Hensley) writes:
- >From: john@clinicom.com (John Hensley)
- >Subject: PC/TCP 2.1 copy protection
- >Date: 8 Sep 92 21:42:08 GMT
- > ......
- >Is anyone else torqued about this, or am I letting my bias against copy
- >protection cloud my judgment of a handy new network management feature? Any
- >suggestions for how FTP could protect their software *without* catching hell
- >from people like me? Just doesn't seem likely, given the nature of the product,
- >but I'd sure like the current policy to change....
-
- >--
- >John Hensley |
- >john@clinicom.com | "You think slower when you graze." -- Holling
- >jhensley@nyx.cs.du.edu |
-
- If you want to avoid copy protection, avoid "Distinct TCP/IP" as well.
- Ted Wright (wright@lims01.lerc.nasa.gov)
-