I just directly and personally witnessed the Automatic Updates system of Windows 10, flashing a computer's firmware without getting any kind of permission for that specific action from the user or system administrator.
The PC in question is a recent-model (less than three months old) Dell desktop, though I'm not sure whether this fact is significant.
I'm not going to explain the implications in detail, because if you don't already have a pretty good idea, you likely wouldn't understand the explanation either.
I don't happen to know whether the motherboard on this model has a backup firmware chip, in case of power outage during flash. Hopefully it should, because that is a reasonably common feature these days. But I don't feel like opening the case to verify it at the moment. Nonetheless, I'm going to give Microsoft the benefit of every doubt here and tentatively assume that surely they are only doing this on systems that have that safeguard. (Not because of virtue, but because of the potential for really nasty bad publicity.)
The stated reason (which was displayed on screen as the flash was happening) is, of course, security; but Microsoft cares about your security like Apple cares about your budget. With that said, I looked at the firmware setup after the flash occurred, and it doesn't seem any more egregious than the usual UEFI setup. I'm tempted to put a small Devuan install on the thing, even though it isn't needed on this system, just to verify that it works as expected; but I don't see any indications in the firmware setup that would suggest a problem in that regard, at this time. Secure Boot is enabled, but it appears to still be possible to disable it. So if this is a major power grab or exclusivity lock, I'm missing something.
But I sure don't like the precedent.
0 comments:
Post a Comment