Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
http://www.theonion.com/content/video/warcraft_sequel_lets_gamers_play?utm_source=videomrss_79397
Basically, you get to play a person who's playing the game.
The benefits of Automatic Updates FAR outweigh the (very small) potential for damage, not so much in businesses where patches are usually rolled out carefully -- but in the residential context and it could very well scare people into turning Automatic Updates off.Agreed. But it's something people, especially businesses, should think about.
Code:Code: [Select]protected virtual void OnConnected(EventArgs e)
{
foreach (EventHandler eh in __Connected[Priority.High])
{
try
{
eh(this, e);
}
catch (Exception ex)
{
ReportException(
ex,
new KeyValuePair<string, object>("delegate", eh),
new KeyValuePair<string, object>("Event", "Connected"),
new KeyValuePair<string, object>("param: priority", Priority.High),
new KeyValuePair<string, object>("param: this", this),
new KeyValuePair<string, object>("param: e", e)
);
}
}
ThreadPool.QueueUserWorkItem((WaitCallback)delegate
{
foreach (EventHandler eh in __Connected[Priority.Normal])
{
try
{
eh(this, e);
}
catch (Exception ex)
{
ReportException(
ex,
new KeyValuePair<string, object>("delegate", eh),
new KeyValuePair<string, object>("Event", "Connected"),
new KeyValuePair<string, object>("param: priority", Priority.Normal),
new KeyValuePair<string, object>("param: this", this),
new KeyValuePair<string, object>("param: e", e)
);
}
}
ThreadPool.QueueUserWorkItem((WaitCallback)delegate
{
foreach (EventHandler eh in __Connected[Priority.Low])
{
try
{
eh(this, e);
}
catch (Exception ex)
{
ReportException(
ex,
new KeyValuePair<string, object>("delegate", eh),
new KeyValuePair<string, object>("Event", "Connected"),
new KeyValuePair<string, object>("param: priority", Priority.Low),
new KeyValuePair<string, object>("param: this", this),
new KeyValuePair<string, object>("param: e", e)
);
}
}
FreeArgumentResources(e as BaseEventArgs);
});
});
}
FatalExecutionEngineError Managed Debugging Assistant comes up with:QuoteThe runtime has encountered a fatal error. The address of the error was at 0x7f578493, on thread 0x14ec. The error code is 0xc0000005. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack.(Note 0xc0000005 is ACCESS_VIOLATION).
I doubt I'll get much help but, thoughts?
Also, yes, if I take out the anonymous delegate calls and make those calls inline without a separate thread, the error goes away.
Do you have a girl (boy?) friend? Yespics or lies
O HAI JEFF
DO I NO U?
http://www.computerbytesman.com/security/windowsupdate.htm
Just think -- if MS sent out a bad update (malicious employee? malware infection?) they could hose the world!
The mitigation is, in my opinion, that a lot of bigger companies (the government I work for for sure) tests each patch before deploying. But it could still be timebombed or something!
I stopped reading at:
"exploited by a disgruntled Microsoft employee"
These people need to read about QA and move on. What, do they sit around all day writing up these silly scenarios so they can put out a meaningless article?
Here's a new an interesting idea, why not turn off the Automatic Updates if you're a big company? Problem solved.
The majority of users will be running Windows Vista in the very near future, which has a lot of added protection against malware and has a great security track record.
In any case, let's take an example of Sony's recent 2.40 patch for their Playstation3, it bricked a lot of PS3s. Did this mean the end of the world? No it simply meant they put out a corrective patch.
Let's take another example of Windows Vista SP1 being shipped with an endless reboot bugs that occured on Frankenstein OEM PCs which had misconfiguration out of the box. What happened? The installs were reverted and the update was pulled for their specific hardware configuration.
In short, there's an inherent and obvious risk associated with Automatic Updates. However, there's an even bigger risk with assuming the majority of users may check for updates by themselves, this has been consistently shown to not be the case.
