methods for putting labels into your software?

Lutz Jaenicke jaenicke at w414zrz.ee.tu-berlin.de
Thu Jun 27 19:06:51 AEST 1991


In article <1991Jun26.165609.9692 at athena.mit.edu> mlevin at jade.tufts.edu writes:
>
>   I'd like to hear suggestions, or any tricks that the pros out there
>know about, for putting some kind of text label or code into your
>executable (compiled and linked from C code) so that if anyone were to
>copy a part of the code, you could know it was a copy by somehow
>seeking out that label. 

>I am looking for
>ideas that are less obvious to detect - a method such that someone
>copying the code wasn't likely to notice and edit out (with a patch or
>something). Any ideas would be appreciated.
>
>Mike Levin

As I understand your problem you want to mark your code with a unique
identifier, which is not obvious but easy to find for you. There are
many ideas which are easy to realise. I would do it by coding my sign
twice into the program, one readable for everyone (normally I'm proud
of my work) and one in a coded form (XORed, backwarded or whatever else):
static char *COPYRIGHT=      "@(#) (c) Lutz Jaenicke etc.";
static char *COPYRIGHT_EXTRA="A)$*!)d*!Mvu{!Kbfojdlf!dud/";
where the second string is just the same replaced by the char in the
ASCII table. The first string is easily found by "what" without problems,
search the second by whatever you want.

Using a coded form of your signature can lead you to just code your
crypt-scheme into your program and check, if a little pig has patched...
One could think of doing nasty things, if..., but that depends on your
problem. I know people, who I'd suppose to patch in their own name and
go shopping with my program. I don't like such people.

Don't get ideas, you are sorry of later,
	Mvu{!Kbfojdlf
-- 
Lutz Jaenicke 				jaenicke at w414zrz.ee.tu-berlin.de 
Institut fuer Elektrische Maschinen	jaenicke at emapollo.ee.tu-berlin.de
Technische Universitaet Berlin		Tel. (004930)314-24552
Einsteinufer 11, D-1000 Berlin 10 	Fax. (004930)314-21133 



More information about the Comp.unix.programmer mailing list