Microsoft to add 'black box' to Windows

There is a key that is missed here, and I approve. IT security managers can set options remotely and redirect the output to their desks. Choosing when, where and what to send either to MS, Security professionals or application developers. Is it a privacy issue? Sure, so is internet monitoring and IDS systems. All for my benefit as a security professional and for the benefit of network integrity. The content has value from security and compliance of policy. Not to mention troubleshooting persistent application crashes that we all run into and MS doesn't have to get a whiff of it unless we approve.

If one doesn't agree, then upon a system crash hit "no" ;)

Quote:

---

Well, if data goes out, then there are always it can come in.

---

Not true. You can block ALL incoming traffic if you wish and still allow complete outbound traffic with a firewall.

Example with iptables:

Code:

---

iptables -A INPUT -j DROP

---

That will drop any incoming packets as soon as they hit the firewall.

Quote:

---

If one doesn't agree, then upon a system crash hit "no

---

My point exactly.

As road has stated..can be used to monitor your network application crashes..set to send to a central server\workstation, reviewed then sent off...I think it would be very handy to know if a new update was knocking out one of our network apps...and crashing machines

I have used this feature on a new 2003 server, I have worked with microsoft techsupport to resolve issues on many occasions
...and can see no reason they have malicious intent here.

I have received excellent tech support from Microsoft, working with me until the issue is resolved...and following up. I have no problems forking out the 245 usd for this kind of support...and have had it refunded when it was found to be caused by a recent update..or is an undocumented bug.

They also dont talk down to me ..because of my gender

Yes as I said in the first post maybe it could be redirected or sniffed.....

So can alot of things..... :rolleyes:


<RANT>
I cant understand why people bitch and complain about MS...then when MS wants to try to work with their customers on resolving some of these issues
and ...they are continually bashed for it.

Personally..if you dont like MS...dont use their product, or support it. Leave all those customers to me $$$$$$$ :cool:

If you are that unhappy with it....do something about it..and install\support something else...
or you can work with MS and try and make the product better..more secure

or just STFU :eek:

If this offends anyone..too fU%^king bad!!!!!

I am in a bad mood!!

<RANT OVER>

MLF

Something else I want to note here, is that while a good deal of people will (in other posts) complain about how often Windows crashes, how many bugs and exploits it contains, and general "windows is broke" posts.... they don't want to take their own time to report the crashes and errors to improve the operating system.

If you want to see windows improved, then send bug reports. You kick and scream if someone compains about open sourcebugs, practically forcing them to file a bug report and read the project WiKi. So now follow your own advice and file the bug reports that windows can send on it's own handy tool.

guardian

I agree with you...

Anyway..an aside

New XP pro installed.....hasnt crashed yet...2 weeks and running...and so far it is the best MS OS I have run

New hardware (good hardware :) )

If it crashes...I will send a report.

MLF

I agree as well. The tool may take in more information initially than it needs to but you do have options as to what to do with it, I just like starting threads along this line because it creates some lively discussion. ;)

Side Note; The only thing I have had crash XP is the way Mozilla handled PDF files.

Hmmm,

I don't think the issue is one of reporting Microsoft bugs. It is more one of the suggestion that this "improved" system will potentially send totally irrelevant but potentially sensitive, compromising or illegal information to persons who have no right to view it (internally or externally)

It should not be up to the user to vet the information being sent, it should not be there in the first place as it serves no useful purpose. By including it you create the potential for error. And the information sent to the IT personnel will not be sanitised, and it may not be apropriate for them to view it?

:)

Quote:

---

compromising or illegal information to persons who have no right to view it (internally or externally)

---

I'm sorry, but I just do not feel sympathy. If you are talking about child porn on AIM, don't send it. If you are downloading 12 mp3 files at once from kazaa, don't send it. If you are having a simple chat with your mother, don't send it.

If you KNOW that the information you have is not illegal in any way, then what is the hold up? Curious as to what it sends out? Then I'm sure a filtering firewall that runs as a passive packet sniffer can show exactally how much information is being released. Chances are, it's not going to be chat logs and folder history, nor internet history and a list of all the installed programs. Chances are it's going to include the information needed to bugtest whatever Microsoft program crashed.

People had the same fear when the first release of bug reporting happened on windows, and the myths of what type of information was released was publically debunked over and over. You have to keep in mind that there is no reason for a developer to have the information from your trillian log files, and it would only hinder his progress to see what caused the Microsoft application (as it only runs ON microsoft applications, not 3rd party applications) to crash. It may be a list of currently running processes, windows version and installed udates, and other things that actually relate to the problem. But it won't be a chat log from you speaking with your mother about shoe sizes.

Whatthe, Nihil, VanEck and everyone else
I didnt mean to offend anyone...

I am just in a REALLY bad mood right now!

I just had a discussion with someone about MS...he hates them ...though he runs a full MS shop....I try and explain that at any time he can switch over to an open source platform....just give me a heads up to look for other work ;)

Yes lively discussions... I like them also.

Some of the security issues are valid....

But...I can see a great benifit to MS and too its customer base to use this type of info.

MHO of course

MLF