🚀 go-pugleaf

-->On Thu, 1 Oct 1992 11:20:19 GMT, deej@cadence.com (Jim Howard) said:

 Jim> In article <davison.716941195@sfu.ca> davison@selkirk.sfu.ca (R. Davison) writes:
>marra@samuel.enet.dec.com (Dave Marra) writes:
>
>>re: talk about moving the system clock back.
>
>>Why can't the license system keep an internal timestamp inside it's license
>>database somewhere, and then, when it detects that time has taken a step
>>backwards, simply disable all licenses?  
>
>The clock on our systems needs to adjusted occassionally.  If I had
>to reinstall all licenced systems every time, I'd be wishing for a
>better scheme.  Licencing, should not inconvenience legitimate users.
>
>>At that point it would take a complete re-installation of the entire license
>>system, including the licenses to get everything back online.  I would think
>>that would deter folks from setting the clock back.
>
>Rod  Davison.
>

Changing the system clock on networked systems is getting harder and
hadrder to do without seriously impacting users. (I suppose if NTP or
some other protocol and internetwork connectivity kepp going, you
system could just check (trusted) NTP time servers for the real time.)
E-mail gets confused, developement operations with make and rcs are
similarly obfuscated.  It's hard for me to change the clock on my
little stand-alone Mac, much less in a workgroup situation. We ship
time based demo keys all the time and if the user wants to change the
system clock to squeeze a little more time out of the key, there's not
much that we want to do to stop him. It just not a big issue for us.


Ken
--

Ken Mayer (ken@visix.com)
Visix Software Inc./703.758.8230
  Bene Vivere Ultio Optima --- Living Well is the Best Revenge