Slashdot Mirror
Microsoft To Add A Black Box To Windows
An anonymous reader writes "According to ZDNet, Microsoft plans to add the software equivalent of a 'black box' flight recorder to Windows. According to the article, 'The tool will build on the existing Watson error-reporting tool in Windows but will provide Microsoft with much deeper information, including what programs were running at the time of the error and even the contents of documents that were being created.'" Commentary available via C|Net as well.
Except the blackbox on a jet won't (unless I'm woefully uninformed more than usual) tell what you were doing in your own seat when the plane went down.
"occupant of 17A was eating peanuts, doing inflight magazine crossword and had dirty underwear"
"Our stance on this is that the user is in control," Sullivan [Windows lead product manager] said. "In the consumer environment, you will be presented with a dialog that clearly gives you the choice whether to share the information and then also provides exactly what the detail is so you can parse character by character what's being sent."
Sounds reasonable, so long as it doesn't hide anything from view. Of course, if you have Visual Studio you can hit Debug and lookie yourself, which is usually more helpful than anything I've ever got back from Microsoft.
The probablem was likely caused by a faulty driver
And consumers could have a tough time knowing just what information they were sending. Though they'll be able to see the contents of a document, they may not recognize the significance of the technical data--such as register settings--that's being sent.
Consumers stick with what works. If hitting Don't Send works, they stick with it. If the problem persists then they'll probably send.
It said, "what we have here is failure to communicate." What's that mean?
A feeling of having made the same mistake before: Deja Foobar
It will record your screams as your computer crashes.
At first I was tempted to do like most: yell out that this was a privacy issue. Microsoft has no right knowing what software I'm using! But there are so many instances where I could claim that my privacy is invaded that I'm afraid I'm becoming more accepting of it.
...". So Steam/Valve know each time I play half-life. Interesting stats for them.
...
The latest of these instances occurred when I fired up Half Life 2 last night. "Logging on to Steam as
Every time I browse a web page, I'm telling everyone I use Firefox/1.0.3 on x64 Linux. Sure, I could hack my user agent string, but really. Most people don't, right? So now the slashdot editors know what I run, what my IP address is,
I only boot to Windows to play games like Half-Life, and it bothers me that Microsoft would know about everything I'm running on that Windows box, but how else are they to fix issues if they don't know what I'm running and what I was doing when it crashed? When do we draw the line between normal computer use and invasion of privacy?
The biggest issue I see with this, at least in the short term, is the possible use of this feature in the corporate setting.
With businesses, however, IT managers typically set the policy. If they wanted total information, they could configure systems so that they'd know not only that a user was running Internet Explorer, for example, but also that he or she was watching a video from ESPN.com. Or, they might find out not only that a worker was running Instant Messenger but also that he or she was talking to a co-worker about getting a new job.
This is a major invasion of privacy if you ask me. Of course, while at work you are using company resources so they really do get to say how and when they are used but I feel there is an important difference between monitoring your employee's resource usage and actually reading their emails and instant messages. You don't have to totally invade everyone's privacy to enforce your company policy of internet usage.
But Sullivan pointed out that businesses can already install third-party software to monitor workers' computer usage and some do.
While the above is most certainly true, having something like this built into Windows by default just makes it that much easier and thus inviting for a company to implement this sort of monitoring. I just can't wait for the day when all employees have a tracking system attached to them at all times and are reprimanded if they spend too much time going to the bathroom or chatting to a coworker. What great fun that is going to be!
Another issue with this that is mentioned in the article is the fact that while you will be able to look through all the data being reported, most people will not have the knowledge to determine how much of it is sensitive.
And consumers could have a tough time knowing just what information they were sending. Though they'll be able to see the contents of a document, they may not recognize the significance of the technical data--such as register settings--that's being sent.
Not everything is totally obvious, such as personal emails or credit card numbers. Not to mention the fact that it will very likely be buried among a lot of other unintelligable data. Also, given the habit of most Windows users of just clicking 'OK' or 'YES' to anything and everything that pops up on their screen, I doubt many people will actually review the information being sent in the report.
Will it survive after I kick the shit out my computer and then throw it off a cliff?
as long as I can shut it off!
Why not make the Whole OS out of the black box stuff? Then nothing can damage it!
Wouldn't it be faster for them to sift through the logs of what was happening when the system was stable? I mean, dear God, imagine the size of the log files if they logged crashes.
If you mod me down, I shall become less powerful than you could possibly imagine.
Except the blackbox on a jet won't (unless I'm woefully uninformed more than usual) tell what you were doing in your own seat when the plane went down.
Pleasuring yourself one last time before you die?
I am defenseless. Use your button. Mod me down with all of your hatred.
Talk about an invasion of your privacy and a HUGE hole to reveal corporate IP. It won't be long until someone invents an hack or virus to exploit this and capture all of what you are working on. I'm supposed to trust that MS won't use any of my info they captured to debug thier software?
That there's nothing compulsory about this, obviously. And furthermore, it appears that the system will be suited to provide for the customer's preservation of personal privacy:
For consumers, the choice of whether to send the data, and how much information to share, will be up to the individual. Though the details are being finalized, Windows lead product manager Greg Sullivan said users will be prompted with a message indicating the information to be sent and giving them an option to alter it, such as removing the contents of the e-mail they were writing when the machine crashed. Also, such reporting will also be anonymous.
The only concern, one might suppose, is for people who don't want this information accumulated should their computer later be searched by others (the law? An employer? A relative?). This is perhaps a legitimate concern, but hard to argue for, as a reason to cripple error reporting.
I think it's awfully interesting that Microsoft has begun announcing tiny feature announcements one by one in a nice string of succession throughout the month of April. And slashdot's just eating it up! They wouldn't be, say, announcing one feature plan at a time for the next 30 day to steal some of Apple's thunder while rolling out OS X Tiger would they? Not a friendly entity like Microsoft?!?!
If you're half as beautiful naked, you'd be 4 times as beautiful with twice as many clothes on.
Personally, I'd draw the line at the point where "opt-in" becomes "opt-out". If the customer is being asked whether they want to send this information to M$, and told just what is being transmitted, then I don't see that much of a problem.
However, it's important that you actually have to acknowledge this - so, for example, the default button (the one that has the focus) should be "No" rather than "Yes", so users actually have to make a conscious decision instead of just saying hitting return because that's what they always do when an error pops up.
In other words, consent is required, but it also has to be informed consent. Someone who just says "Yes, do this" because they don't understand what's going on and what the implications are does not consent IMO.
quidquid latine dictum sit altum videtur.
I can just see it. Clippy will get replaced by a stern man's face watching you. The power switch to the monitor will no longer work...
The truth is an offense, but not a sin.------R. N. Marley
"When do we draw the line between normal computer use and invasion of privacy?"
When information is reported without your consent.
Beauty is in the eye of the beerholder.
it was from "cool hand luke"
the prison guard talking to/about paul newman
http://imdb.com/title/tt0061512/quotes
-- it's ridiculous how many people misspell ridiculous... (damn, damn, damn...)
When the vendor leverages the market information to make the decision for you that you should upgrade, I daresay you may feel invaded, while falling short of concluding whether or not Daddy Knows Best.
Time will Tell.
Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
Plus, Qui custodet ipsos custodies? Microsoft just created a new target for hackers, both writing to (for hiding their own tracks) and reading from (for extracting information when searching for personal user information.) Not insurmountable problems, but will M$ think to solve them before being bit on the backside?
One step forward, two steps back...
//Information does not want to be free; it wants to breed.
Or is it already?
If sending your computer's configuration to Microsoft in the background was found to be illegal by the courts back in the Win95 days...
Wouldn't sending configuration information PLUS document contents be considered illegal today?
I mean, come on now, this couldn't possibly be happening, and out in the open to boot?
...
the choice of whether to send the data, and how much information to share, will be up to the individual
Looks like Microsoft is fine, then.
C'mon, man. If the plane's going down, even a slahdork could probably find some girl on the plane who would be interested in a final go-round. Don't underestimate the power of impending death. It might be your best hope for losing your virginity.
You know what?
Strawman. This isn't about giving my address to someone, this is about potentially telling them every detail of what I sent through the mail, including credit card information, private letters to loved ones, potentially sensitive business documents, etc.
The concern isn't that a stack trace might be sent to MS -- it's that they want to have a copy of any document open on one's computer at the time. For now, we can turn it off. But, it pays to keep an eye on things to make sure we can always turn it off. After all, how would you like it if it came out that you had a confidential illness because a medical transcriptionist hit 'Send' after Word crashed while mail-merging your test results?
We may not imagine how our lives could be more frustrating and complex—but Congress can. – Cullen Hightower
"After all, how would you like it if it came out that you had a confidential illness because a medical transcriptionist hit 'Send' after Word crashed while mail-merging your test results?"
Which brings up HIPPA concerns, here in the US.
With this concern, and given the stringent regulations that hospitals and health care providers have to obey, it should be mandatory that this feature be turned off permanently and irrevocably at install time for any system purchased by any health care provider. If this technology is even available on the computers they use, hospitals are opening themselves up to massive liability.
You can a floor nurse working at the same time next to another nurse who has a patient with an unusual disease. If you log in and look up the patient's record--or even look over the shoulder of your coworker when he logs in--the hospital is liable under HIPAA for privacy violations. They can be fined, and they can be sued, and enforcement of these rules happens frequently. Now imagine what could happen if THIS system is used in a hospital computer!
It's rare that you're presented with a knob whose only two positions are Make History and Flee Your Glorious Destiny.
Canada's Personal Information Protection and Electronic Documents Act (PIPEDA) expressely forbids the external transmission of client data, which would no doubt include the documents on our firm's computers, without their consent.
I can't see too many of our clients agreeing to let the confidential contents of their documents be sent to Microsft to figure out why our PCs crashed.
If you don't want to repeat the past, stop living in it.
I wonder if it will survive the crash.
If this tool is really to catch errant drivers, it's usually pretty serious for the OS to throw up its hands.
I wonder if the OS will maintain enough smarts to flush the BSOD information and other stuff to disk properly.
For that matter, if it's not a critical driver (e.g. a sound card driver or network card driver, etc), that goes wonky, why BSOD completely? Why can't the OS log a critical message stating 'This driver encountered an unrecoverable error and has been disabled'. Please close what you were doing and reboot *NOW*'.