Name: APK 2009-02-28 22:15
I have a question to ask...
Do ANY of you folks have an answer, a GOOD SOLID TECHNICAL answer, as to WHY these cripplings have been implemented in VISTA, Server 2008, & most likely their
descendant, in Windows 7:
----
1.) The removal of being able to use 0 as a blocking IP address in a HOSTS file
(vs. 0.0.0.0 or 127.0.0.1, which are bigger, slower on load into the local DNS Cache (as well as slower flushes via ipconfig /flushdns) & also occupy more RAM once loaded, for NO GOOD REASON - 0 blocks as well as the other 2 do, & is smaller + faster!)
In this case, this happened on 12/09/2008 Microsoft "Patch Tuesday" updates, it wasn't LIKE that before then!
E.G.-> Here, using 0 as my blocking IP address in a FULLY normalized (meaning no repeated entries) HOSTS file with nearly 650,000 bad sites blocked in it, I get a 14++mb sized HOSTS file... using 0.0.0.0 it shoots up to 18++mb in size (& even worse using 127.0.0.1, to around the tune of 24++mb in size)... Here? This is SENSELESS bloat creation as the result!
&
2.) The removal of IP Port Filtering GUI controls for it via Local Network Connections properties "ADVANCED" section
(This is up there w/ when MS removed the GUI checkbox after NT 4.0 for IP Forwarding, only, this time, the difference is (and, it's a PAIN) is that it is NOT a single 1 line entry to hack via regedit.exe, but FAR MORE COMPLEX to do by hand)... Port Filtering is a USEFUL & POWERFUL security (& to a degree, speed also) enhancing feature!
Afaik, on THIS case (vs. #1 above)? It has always been that way in VISTA &/or Windows Server 2008... & not just the result of a Patch Tuesday modification.
----
I posted on Mr. Sinofsky's (?) blog -> http://blogs.msdn.com/e7/archive/2009/02/25/feedback-and-engineering-windows-7.aspx [msdn.com]
AND, I have YET to get a SOLID TECHNICAL ANSWER on those things going on in VISTA, Server 2008, & probably Windows 7 as well, that justify doing so...
(They're things I'd really LIKE to get an answer to, as to WHY Microsoft has done the 2 things in my list above, to the above noted versions of Windows)
Sorry Microsoft - I really like your OS & softwares, but this time? Well - Both of those being done? EXTREMELY STUPID!
APK
P.S.=> Does ANYONE know why these STUPID things were done to the latest/greatest versions of Windows? I don't...
Otherwise, consider this "ammo" you 'anti-microsoft/anti-Windows' *NIX fans here can use, because @ this point? I wouldn't blame you IF you did... & hopefully??
It helps FORCE MS to undo them... because, I will be COMPLETELY FORTHRIGHT about this much: They're 2 reasons I won't upgrade beyond Windows Server 2003... apk
Do ANY of you folks have an answer, a GOOD SOLID TECHNICAL answer, as to WHY these cripplings have been implemented in VISTA, Server 2008, & most likely their
descendant, in Windows 7:
----
1.) The removal of being able to use 0 as a blocking IP address in a HOSTS file
(vs. 0.0.0.0 or 127.0.0.1, which are bigger, slower on load into the local DNS Cache (as well as slower flushes via ipconfig /flushdns) & also occupy more RAM once loaded, for NO GOOD REASON - 0 blocks as well as the other 2 do, & is smaller + faster!)
In this case, this happened on 12/09/2008 Microsoft "Patch Tuesday" updates, it wasn't LIKE that before then!
E.G.-> Here, using 0 as my blocking IP address in a FULLY normalized (meaning no repeated entries) HOSTS file with nearly 650,000 bad sites blocked in it, I get a 14++mb sized HOSTS file... using 0.0.0.0 it shoots up to 18++mb in size (& even worse using 127.0.0.1, to around the tune of 24++mb in size)... Here? This is SENSELESS bloat creation as the result!
&
2.) The removal of IP Port Filtering GUI controls for it via Local Network Connections properties "ADVANCED" section
(This is up there w/ when MS removed the GUI checkbox after NT 4.0 for IP Forwarding, only, this time, the difference is (and, it's a PAIN) is that it is NOT a single 1 line entry to hack via regedit.exe, but FAR MORE COMPLEX to do by hand)... Port Filtering is a USEFUL & POWERFUL security (& to a degree, speed also) enhancing feature!
Afaik, on THIS case (vs. #1 above)? It has always been that way in VISTA &/or Windows Server 2008... & not just the result of a Patch Tuesday modification.
----
I posted on Mr. Sinofsky's (?) blog -> http://blogs.msdn.com/e7/archive/2009/02/25/feedback-and-engineering-windows-7.aspx [msdn.com]
AND, I have YET to get a SOLID TECHNICAL ANSWER on those things going on in VISTA, Server 2008, & probably Windows 7 as well, that justify doing so...
(They're things I'd really LIKE to get an answer to, as to WHY Microsoft has done the 2 things in my list above, to the above noted versions of Windows)
Sorry Microsoft - I really like your OS & softwares, but this time? Well - Both of those being done? EXTREMELY STUPID!
APK
P.S.=> Does ANYONE know why these STUPID things were done to the latest/greatest versions of Windows? I don't...
Otherwise, consider this "ammo" you 'anti-microsoft/anti-Windows' *NIX fans here can use, because @ this point? I wouldn't blame you IF you did... & hopefully??
It helps FORCE MS to undo them... because, I will be COMPLETELY FORTHRIGHT about this much: They're 2 reasons I won't upgrade beyond Windows Server 2003... apk