🚀 go-pugleaf

I have been trying to think of a method to keep a handle on some software that
I have in the field.

What I would like to do is be able to authorize a site with a timestamp (long
integer in the form of a string) so that the software would stop working after
a certain period of time.  My problem is that I can't seem to think of a way of
implementing it where the software at the remote site wouldn't have the key
(unencrypted).

What I would like to do is uucp out a crypted key that corresponds to a date
past which the software would stop operating.  If the key were based on the
remote site's uucpname it would prevent copying of the software (more or less)
as well; they would either have to have the same name or apply for their own
key.

Of course, the problem of their patching the binary to ignore the check for the
timestamp is another question entirely... but anyhow, any thoughts on this?

Jon
-- 
Jon Boede		jboede@auscso.UUCP, jon%bodedo@im4u.cs.utexas.edu
1301 Trace Dr. #204, Austin, TX 78741-1735		(512) 462-3287
	"People who are incapable of making decisions are
	 the ones that hit those barrels at freeway exits."