I love that article.
QUOTE
The issue won’t affect OEM users who buy new workstations with OEM software pre-installed, but will catch corporate users upgrading from XP. It could lead to piracy claims against upgrading companies. At best resources will be tied up sorting out the mess. Not good.
Any IT staff upgrading to Vista and cought off-guard by this (either at RTM or now) should be ashamed of themselves. All it takes is a KMS server and your KMS keys to bypass this. Not to mention the BIGGEST gaping hole in the antipiracy initiatives of XP / 2003 and older was the VLK product key not requiring activation, and this was well documented and passed on to shops with SA agreements (and to the internet as a whole) that this WAS going to change in Vista and Server 2008. Any shop who does their research before rolling a major upgrade out would no doubt NOT be caught by this. A non-starter and sensationalism at best.
QUOTE
Symantec have just produced an excellent report into a number of serious flaws in Microsoft much-hyped secure operating system. They’ve found that far from protecting users from common virus and trojan infections, Vista actually poses a higher risk by giving users false assurances of protection.
Symantec lab-tested 2,000 common varients of malicious code, like backdoor, keylogger, rootkit, mass mailer, Trojan, spyware, adware and unsorted. They installed them as a user might, watching how Vista handled them. They tested if they could run and if they could survive a re-boot.
Yes, that's the key phrase there, "as a user
might", most likely clicking the "allow" button in the UAC dialog. I make this assumption based on the results, especially changing protected reg keys - this can ONLY happen if the admin allows it by disabling UAC or clicking "allow" when prompted, because these accesses always trigger UAC. This is of course what some people will do when presented with the dialog if they aren't paying attention, and yes, bound to be a problem. If someone says "yes, please install this virus as the sysadmin", what do you expect to happen? I'm sorry, but users CANNOT be saved from themselves if they aren't willing to be a part of security (security is something you do, not something you buy or some software you run, for goodness' sakes), and this isn't a Microsoft problem per-se. It's why companies like Symantec have a place in the world. If the user had clicked "don't allow" in the UAC dialog, I'd wonder how many of these (at RTM) would have installed and run, and I'm even more interested at SP1 if this would have changed. Again, a bit of sensationalism (yes, a security study sponsored by an antivirus vendor, no conflict of interest - let's spout it as fact!!!).
QUOTE
A Symantec technical source has said “The implication is that the vast majority of Windows Vista hosts are, by default, remotely accessible via IPv6 and Teredo”.
This places a serious risk on a conventionally-protected network. Microsoft have concentrated on protecting their marketing advantage and not consulted network standards and security authorities before releasing this feature.
Sheesh - Teredo is IPv6 tunneling to another IPv6 host over an IPv4 network. Yes, it'll bypass IPv4 firewalls and routers if they allow the IPv4 traffic (like all other IPv4 traffic that's allowed, btw), but the end host has to be an IPv6 host to receive the packets, and it is hopefully running a firewall that can accept the IPv6 traffic tunneled over IPv4. The traffic tunneled over IPv4 will then pass through the firewall on the host once it's back to IPv6 traffic (if Vista or another host with an IPv4 and IPv6 firewall), so I fail to grasp the "problem" here. If someone turns the Windows firewall off, or installs an IPv4 only firewall, then yes, this is a possibility, and one that should be thought out and prevented when you enable IPv6 on a host! As to enabling it, eventually you have to enable IPv6 on clients by default, or we aren't going to get there fast enough (and no, I fail to see how enabling IPv6 causes a security risk because only other hosts running IPv6 can talk to the Vista box over IPv6 (regardless of whether it's tunneled or straight IPv6, and the admin should have already secured those machines, dammit). Another "sensationalism" meant to scare you, when in fact, IPv6 and IPv4 are firewalled on Vista hosts by default, so I see this as yet another non-issue.
QUOTE
Instead of offering Vista users a higher level of security than XP, Microsoft is actually exposing them to further and far more sinister risks with Vista. And that is unforgivable.
The only thing unforgivable is the unresearched and obviously biased opinions from this site on the issue(s). Don't believe everything you read, kids.