Hi,
Are you trying to prevent this change to protect against “malicious”
changes, or simply so that all your machines can have the same time? If
it’s the latter, then setting the policy and telling your users a
message (“Please don’t change the time”) should be enough. I don’t see
why a user would start messing around with the computer, disable the
policy, and change the time, unless he has malicious intent.
Which gets me to my second point. If you’re trying to block malicious
users, then there’s nothing you can do, since you seem to be letting
them run in administrator mode (since they can change the policy/time).
Even if you were to write a driver to reset the time on an “unauthorized
change” (which would already be an ugly hack), nothing stops your
malicious user from unloading your driver, or getting around it using a
myriad of methods available to an admin.
So again, if this is casual blocking – inform your users and set the
policy. If this is anti-malicious blocking – don’t allow rogue users to
have administrator access to the machine.
Best regards,
Alex Ionescu
Steve Spano wrote:
That’s pretty handy - the driver knowing the time has been changed.
Thanks for sharing that!
So, couldn’t your driver trap on when the time was changed and either
reset the PC’s clock based on the US’s atomic clock website? Or what if
your driver polls the time every minute and then if it sees the time
changed, it updates the clock based on the last time sample?
Steve Spano
President, Finger Lakes Engineering
(V) 607-277-1614 x223
(F) 800-835-7164
(C) 607-342-1150
xxxxx@flconsult.com
www.fl-eng.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Tuesday, February 21, 2006 7:32 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Prevent changing time.
As has already been stated you cannot stop people from changing time.
You
can make a driver that lets you know time has changed. Look at the
ExCreateCallback function to get you started on the driver.