Well, i’am using an old radar detector named Cobra, which was
way good for the old radar’s that the police’s cars were having,
but now with the new radars that have the POP technology,
i think i may gat a Valentine One as in the following video
Microsoft has announced the restoration of Sidekick users’ contacts as the first milestone in recovering data it lost in the cloud computing disaster affecting its Danger subsidiary, while a new source explains why the restoration was possible without a backup and why it is taking so long.
A source familiar with Sun SAN hardware used in the Danger datacenter has provided AppleInsider with additional insight explaining why it is taking Microsoft weeks to recover its users’ lost data after initial reports stated that the data was completely lost and that no suitable backup existed.
Microsoft’s problems began at the beginning of the month, when the cloud servers its operates under contract to T-Mobile began falling offline. It was initially announced that large amounts of T-Mobile’s Sidekick subscribers’ data had been lost and that no backup existed for the user data, which was stored entirely on Microsoft’s servers. (Sidekick devices are not designed to backed up locally in the same way the iPhone backs itself up to iTunes on the user’s desktop computer.)
On October 6, T-Mobile issued a statement saying, “Regrettably, based on Microsoft/Danger’s latest recovery assessment of their systems, we must now inform you that personal information stored on your device – such as contacts, calendar entries, to-do lists or photos – that is no longer on your Sidekick almost certainly has been lost as a result of a server failure at Microsoft/Danger.”
On October 15, two weeks after the problems began, Roz Ho, Microsoft’s vice president of Premium Mobile Experiences, issued an apology for the outage and announced that the company had determined that, contrary to initial reports that all the data was permanently lost, the company now thought that it should actually be able to recover most of the data that had been lost, but that the recovery effort would take some time.
More »
Mozilla has temporarily disabled Microsoft’s WPF plugin for Firefox in order to protect users from a security vulnerability that was recently uncovered in the component. The vulnerability can be exploited when users visit malicious Web pages that contain specially crafted XAML content.
Microsoft issued an Internet Explorer patch to fix the vulnerability through its Windows Update mechanism on Tuesday. The IE patch is said to fully resolve the vulnerability for Firefox users in addition to users of Microsoft’s own browser. Mozilla is concerned, however, that not all users have performed the Windows update yet. In order to protect users who are not yet patched, Mozilla has added Microsoft’s plugin to its add-on blocklist, causing it to be automatically disabled by the browser.
Mike Shaver, Mozilla’s vice president of engineering, described the security problem in a blog entry posted Friday in the official Mozilla security blog. He explains that Mozilla decided to block the plugin when Microsoft suggested that users should consider turning it off until the efficacy of the fix has been fully confirmed. The related .NET Framework Assistant add-on was initially blocked too, but Mozilla removed it from the blocklist when Microsoft later confirmed that it was not vulnerable.
“Because of the difficulties some users have had entirely removing the add-on, and because of the severity of the risk it represents if not disabled, we contacted Microsoft today to indicate that we were looking to disable the extension and plugin for all users via our blocklisting mechanism,” he wrote. “Microsoft agreed with the plan, and we put the blocklist entry live immediately.”
The plugin generated controversy earlier this year because Microsoft surreptitiously injected it into Firefox via a Windows Update, without prompting or notifying users. In response to criticism from Firefox users and concerns expressed by Mozilla itself, Microsoft released a tool in June that users could run to uninstall the plugin.
Adding the plugin to a blocklist seems reasonable in light of the risk that this security vulnerability poses to users, but it’s a very blunt weapon. Microsoft apparently doesn’t properly maintain version numbers in the plugin, so Mozilla has no way to selectively target the block to the insecure version. This means that the block will affect users who have already updated to a safe version of the plugin.
One of our readers submitted a report in Mozilla’s bug tracking system requesting that the plugin be restored for users who are fully patched, but there’s currently no way to accomplish this. Mozilla has implemented a feature in Firefox that will allow users to manually override the block for individual plugins, but it’s unclear when this feature will be deployed. Although it’s likely that it will go out soon in a Firefox update, users may have to wait for its arrival (or dive into about:config and disable the entire blocklist mechanism) if they want to use the WPF plugin.
Plugin security vulnerabilities are a major problem for browser vendors. These bugs are especially tempting as exploit targets because they often affect multiple browsers and provide a bigger audience of potential victims. In response to the serious security vulnerabilities that have been found in Adobe Flash and other popular plugins, Mozilla launched a new plugin check service earlier this month that will help users determine when they need to update. The recent problems with Microsoft’s plugin demonstrate the importance of this sort of vigilance.
Tags: Mozilla disables vulnerable Microsoft plugin for Firefox