Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ucbvax!RELAY.CS.NET!kossmann%wnre.aecl.cdn%ubc.CSNET
From: kossmann%wnre.aecl.cdn%ubc.CSNET@RELAY.CS.NET.UUCP
Newsgroups: mod.computers.vax
Subject: VAX SOFTWARE PROTECTION SCHEMES
Message-ID: <50*kossmann@wnre.aecl.cdn>
Date: Mon, 16-Feb-87 20:26:59 EST
Article-I.D.: wnre.50*kossmann
Posted: Mon Feb 16 20:26:59 1987
Date-Received: Tue, 17-Feb-87 07:27:11 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 7
Approved: info-vax@sri-kl.arpa

Some of our people are getting into the business of selling software, and
would like to implement software protection mechanisms:
	-	some serial number checked by the software
	-	yearly maintenance agreements & fees
	-	blowup dates
Anybody out there have any reasonably secure general mechanisms that could
be considered for VAX software?