Robert McLaws: FunWithCoding.NET

Public Shared Function BrainDump(ByVal dotNet As String) As [Value]

News

<script type="text/javascript"><!-- google_ad_client = "pub-4330602465258980"; google_hints = "ASP.NET, VB.NET, C#, C#.NET, WindowsForms, .NET Framework, VS2005, Visual Studio, XAML, WinFX, Windows Workflow, WPF, WCF, Atlas, NetFX3, Visual Studio Orcas"; google_ad_width = 120; google_ad_height = 240; google_ad_format = "120x240_as"; google_ad_type = "text_image"; google_ad_channel ="4997399242"; google_color_border = "B6C9E7"; google_color_bg = "EFEFEF"; google_color_link = "0000FF"; google_color_text = "000000"; google_color_url = "002C99"; //--></script> <script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"> </script>
<!--
-->

You should feel free to challenge me, disagree with me, or tell me I'm completely nuts in the comments section of each blog entry, but I reserve the right to delete any comment for any reason whatsoever. That said, I will most likely only delete abusive, profane, rude, or annonymous comments, so keep it polite, please.

Blogroll

Cool .NET Articles

My .NET Tools

My Builder.com Articles

My MSKB Articles

Firefox NOT Most Secure Browser Ever

A new vulnerability was announced for all Mozilla-based browsers. Apparently they are vulnerable to phishing attacks just like everyone else. Looks like the rose-colored glasses are coming off. Source: Neowin

Comments

Steve Maine said:

# February 8, 2005 3:49 PM

Steve Maine said:

No installer though :(
# February 8, 2005 3:50 PM

Frans Bouma said:

in address bar, type:
about:config

browse down to:
network.enableIDN
set value to false.
close browser, restart browser, fixed.

# February 8, 2005 5:09 PM

Christian Romney said:

Try fixing IE that way.
# February 8, 2005 5:35 PM

Tyler Brown said:

IE isn't vulnerable to this as they don't support the IDN feature. Firefox will be shipping version 1.0.1 with the IDN feature disabled by default.
# February 16, 2005 3:14 PM

jayson knight said:

Interesting...it appears that IE's lack of "keeping current" actually helped it out on this one.

The actual flaw doesn't lie in the browsers themselves, it lies with IDN itself, so the powers that be at Verisign should be taken out back and shot (don't kill the messenger).
# February 27, 2005 5:19 PM