cjb@ccice6.UUCP (Curtis J. Braun) (08/08/85)
With all this talk about dongles and protection schemes, I was wondering if the dongle method would prevent the use of an Emulator. I am using an Apllied Microsystems emulator to aid me in doing some real time debugging of value added hardware and software for my PC. If I were to use a dongle protected sofware package, would I have to disconnect my emulator?? If I do not need to remove it, then I could also use it to "debug" the software to by-pass the dongle and/or copy the protected code to non-target-ram and alter it. This is only an opinion expressed by myself and not connected to any other real body, and I have no desire to my emulator in a "naughty" way...
slerner@sesame.UUCP (Simcha-Yitzchak Lerner) (08/11/85)
> With all this talk about dongles and protection schemes, > I was wondering if the dongle method would prevent the > use of an Emulator. I am using an Apllied Microsystems > emulator to aid me in doing some real time debugging > of value added hardware and software for my PC. If I > were to use a dongle protected sofware package, would I have > to disconnect my emulator?? > If I do not need to remove it, then I could also > use it to "debug" the software to by-pass the dongle and/or > copy the protected code to non-target-ram and alter it. > As I have said before, a properly designed key system would be truely patch proof. With several critical (but inobvious) routines EXECUTING in the key, patching would be non-productive (eg: the program wouldn't check the key, but it also wouldn't run :-) As to figuring out what the key is doing, with enough dummy params going back and forth, and routine to routine ID mapping being variable, it would be more work to crack the system than to write the entire application from scratch... -- Opinions expressed are public domain, and do not belong to Lotus Development Corp. ---------------------------------------------------------------- Simcha-Yitzchak Lerner {genrad|ihnp4|ima}!wjh12!talcott!sesame!slerner {cbosgd|harvard}!talcott!sesame!slerner slerner%sesame@harvard.ARPA