Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ucsfcca.UUCP
Path: utzoo!linus!decvax!ucbvax!ucsfcgl!ucsfcca!dick
From: dick@ucsfcca.UUCP (Dick Karpinski)
Newsgroups: net.micro.pc
Subject: Re: software protection - dongles
Message-ID: <389@ucsfcca.UUCP>
Date: Fri, 19-Jul-85 21:05:57 EDT
Article-I.D.: ucsfcca.389
Posted: Fri Jul 19 21:05:57 1985
Date-Received: Sun, 21-Jul-85 21:26:22 EDT
References: <566@alberta.UUCP> <5100083@uiucdcsb> <94@duvel.UUCP>
Reply-To: dick@ucsfcca.UUCP (Dick Karpinski)
Organization: UCSF Computer Center
Lines: 18

In article <94@duvel.UUCP> frans@philmds.UUCP (Frans Meulenbroeks) writes:
>The main disadvantage, I see, is that every product uses its own dongle,
>and therefore one has to switch dongles too often. Therefore, the dongle

As one of the (probably parallel) inventors of the dongle, I can say
that this problem was thought through.  First, any dongle should only
respond when the port is not otherwise being used, eg only when DTR
and DSR are both off.  Secondly, it should respond only to a specific
request sequence.  Thus if you have six of them, one after another in
a daisy chain, each will respond only to its own software and all will
be well.  OK?

Dick
-- 
Dick Karpinski    Manager of Unix Services, UCSF Computer Center
UUCP: ...!ucbvax!ucsfcgl!cca.ucsf!dick   (415) 666-4529 (12-7)
BITNET: dick@ucsfcca   Compuserve: 70215,1277  Telemail: RKarpinski
USPS: U-76 UCSF, San Francisco, CA 94143