Xref: utzoo comp.unix.programmer:2147 comp.lang.c:40490
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!emory!utkcs2!jamsun.ic.ornl.gov!mullens
From: mullens@jamsun.ic.ornl.gov (James A. Mullens)
Newsgroups: comp.unix.programmer,comp.lang.c
Subject: Re: methods for putting labels into your software?
Message-ID: <1991Jun26.192319.26495@cs.utk.edu>
Date: 26 Jun 91 19:23:19 GMT
References: <1991Jun26.165609.9692@athena.mit.edu>
Sender: usenet@cs.utk.edu (USENET News Poster)
Distribution: usa
Organization: Univ of TN, Knoxville - CS Department
Lines: 26

In article <1991Jun26.165609.9692@athena.mit.edu>, mlevin@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. For example, I guess you could probably define
|> a static string in your C program which contained a code word, and
|> then you could know if a given program was copied from yours by
|> doing "strings a.out | grep keyword" or something.  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

How about a static long int initialized to your social security
number?  To make finding it in a binary file easier you might
declare a struct with 2 or 3 such unique numbers, but I think most
people's social security number would be unique enough by itself.

-- 
jim mullens
oak ridge national laboratory
mullens@jamsun.ic.ornl.gov (128.219.64.31)
615-574-5564