[NTLUG:Discuss] HIPPA compliance -vs- M$ - Simulating M$ responses

[kbrannen@gte.net]

Steve Baker wrote:
...
> But isn't it the case that modern Windoze machines check back with the Borg
> collective on some kind of regular basis - and that there are 
> 'consequences'
> if they can't get through.  We hear stories of laptops being unplugged from
> their docking stations and taken offline - then when the OS is rebooted, it
> sees a big change in hardware setup - so it tries to talk to M$ HQ and when
> it fails, it assumes it's been pirated and comes up in some deliberately
> crippled mode.
> 
> Blocking that traffic might well be a breach of your EULA on some of these
> machines also.  Aren't there clauses in the EULA now that require you
> to allow M$ entry into your system for security update reasons?  That
> too would be a HIPPA issue because some future update could just as
> easily start routing that handshake stuff to a different domain.
...

Just don't connect the machines to the internet.  The "air-gap" is the best 
defense against the ugly outside world.  Works for any OS (to be slightly 
on-topic).

We have 1 XP (home) machine at my church that is stand-alone.  Ignoring XP's 
quirks, it functions just fine.

I haven't seen the EULA, and I don't care to.  It was legally bought and paid 
for; and I personally don't believe they're legally valid anyway.

Definitely straying so no more from me here, but FYI...

Kevin