Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!uwm.edu!lll-winken!ctrsol!srcsip!gorby!mnkonar From: mnkonar@gorby.SRC.Honeywell.COM (Murat N. Konar) Newsgroups: comp.sys.next Subject: Re: NeXT Software Distribution Message-ID: <33442@srcsip.UUCP> Date: 2 Oct 89 23:33:33 GMT References: <32739@cornell.UUCP> <2235@hydra.gatech.EDU> Sender: news@src.honeywell.COM Reply-To: mnkonar@gorby.UUCP (Murat N. Konar) Distribution: comp Organization: Honeywell Systems & Research Center, Camden, MN Lines: 20 In article <2235@hydra.gatech.EDU> scott@prism.gatech.EDU () writes: [discusion of software keys that are unique for each machine] > In both these cases, the key could be issued based on the hostid > of the system. The hostid is unique to each system. It could also > be based on the ethernet address, which would again be unique to > each system. If the hostid is not hardcoded into the machine, I guess it would be ok. What really sucks is something like what Mentor Graphics does which is setup authorization codes that are dependent on the hard- wired nodeID of the Apollo workstation. When that workstation breaks down, your software is unusable on any other node! Disclaimer: I'm no UNIX dude (I don't even play one on TV) so forgive me if my naivete is showing. ____________________________________________________________________ Have a day. :^| Murat N. Konar Honeywell Systems & Research Center, Camden, MN mnkonar@SRC.honeywell.com (internet) {umn-cs,ems,bthpyd}!srcsip!mnkonar(UUCP)