Amazon’s Kindle Fire now the #1 Android tablet



Data published by comScore shows that Amazon’s Kindle Fire has emerged as the dominant Android-based tablet. At the end of February, the Kindle Fire accounted for 54 percent of all Android tablets. The next most popular Android tablet product line is Samsung’s Galaxy Tab family, which dropped from 23 percent of Android tablets in December to 15 percent in February.

The success of the Fire is no surprise to those paying attention to the tablet market—as we wrote last year, there is healthy demand for a low-cost iPad alternative. Amazon can afford to offer the hardware at a lower price than its rivals because it can make up the difference in content sales. The key factors driving sales of the Fire are likely its low price point, the strength of the Kindle brand, and the breadth of the Amazon content ecosystem.

Read the rest of this article...

Read the comments on this post

Link:
Amazon’s Kindle Fire now the #1 Android tablet

Flashback bots search Twitter for controllers, hit Snow Leopard hardest



Malware investigators for the Russian antivirus company Dr. Web report that the latest version of Flashback, the backdoor malware targeting Macs through a Java exploit, is using Twitter as a backup command and control network.

Dr. Web was the first to report on the rapidly growing Flashback botnet—the largest recorded malware attack ever focused on Macs. In an analysis of current variants of the malware, Dr. Web’s team found that the Trojan software installed through the Java exploit is initially configured with a list of servers through which it can receive additional commands and configuration updates. If the malware doesn’t get a correct response from one of the control servers in its own internal generated list, it will search Twitter for posts containing a string of text generated from the current date, and look for a control server address embedded in the posts.

“For example, some Trojan versions generate a string of the ‘rgdgkpshxeoa’ format for the date 04.13.2012,” the Dr. Web team wrote in their blog post. “If the Trojan manages to find aTwitter message containing bumpbegin and endbump tags enclosing a control server address, it will be used as a domain name.”

The Dr. Web team started using Twitter posts in an effort to “sinkhole” the botnet on April 13. But by the next day, the Twitter account they were using was blocked.

As ComputerWorld’s Greg Keizer reports, the largest percentage of Flashback-infected Macs—63.4 percent of them—are running Mac OS X 10.6 (Snow Leopard). Snow Leopard was the last version of Mac OS X to ship with Java installed. It represents just over 40 percent of the Mac OS installed base, according to data from the market share metrics firm Net Applications. Lion (Mac OS X 10.7), by comparison, accounted for nearly as many systems, but only for 11.2 percent of Flashback-infected systems. It doesn’t come with Java pre-installed.

The connection may have less to do with Java being pre-installed, and more to do with user habits. As Ed Bott pointed out in a Friday blog post on ZDNet, the Dr. Web data also showed that users of older versions of Mac OS X were less likely to have applied software updates. “Nearly 24 percent of all infected Macs running Snow Leopard in this sample were at least one version out of date, and more than 10 percent of those users had skipped three or more major updates,” Bott wrote.

Read the comments on this post


See the article here:
Flashback bots search Twitter for controllers, hit Snow Leopard hardest

Google Releases Full Report On Street View Investigation, Finds That Staff Knew About Wi-Fi Sniffing

evilbear

Earlier today Google released the full report of the FCC’s investigation into the collection of “payload data” from open Wi-Fi networks — aka passwords, email and search history from open networks — that its fleet of Street View cars obtained between 2008 and April 2010. An earlier and heavily redacted version of the report was released on April 15 but today’s version only redacted the names of individuals.

The report found no violation of any wrong doing by the company because there was no legal precedent on the matter. The FCC found that Google did not violate the Communications Act citing the fact that Wi-Fi did not exist when it was written. However, the FCC did fine Google $25,000 for obstructing the investigation, which was presumably the outcome of Google refusing to show the FCC what the data being collected entailed because it might have shown that the company broke privacy and wiretapping laws. Google says any obstruction was result of the FCC dragging out the investigation. Interestingly enough, the report did reveal that the data harvesting was not the act of a rogue engineer and that said engineer notified the Street View team of what was going on.

(Wait. What? Google knew this was going on! It gets even better.)

Except that those members of the team told the FCC that they had no idea it was going on even though the engineer in question sent documentation of the work being done to the entire Street View team in October of 2006. The report also found that up to seven engineers had “wide access” to the plan to collect payload data dating back to 2006.

From the report:

In interviews and declarations, managers of the Street View project and other Google employees who worked on the project told the Bureau they did not read Engineer Doe’s design document. A senior manager of Street View said he “pre-approved” the design document before it was written. One engineer remembered receiving the design document but did not recall any reference to the collection of payload data.

For a little more background, let’s examine what Alan Eustace, Senior VP, Engineering & Research blogged back in 2010:

Nine days ago the data protection authority (DPA) in Hamburg, Germany asked to audit the WiFi data that our Street View cars collect for use in location-based products like Google Maps for mobile, which enables people to find local restaurants or get directions. His request prompted us to re-examine everything we have been collecting, and during our review we discovered that a statement made in a blog post on April 27 was incorrect.

In that blog post, and in a technical note sent to data protection authorities the same day, we said that while Google did collect publicly broadcast SSID information (the WiFi network name) and MAC addresses (the unique number given to a device like a WiFi router) using Street View cars, we did not collect payload data (information sent over the network). But it’s now clear that we have been mistakenly collecting samples of payload data from open (i.e. non-password-protected) WiFi networks, even though we never used that data in any Google products.

However, we will typically have collected only fragments of payload data because: our cars are on the move; someone would need to be using the network as a car passed by; and our in-car WiFi equipment automatically changes channels roughly five times a second. In addition, we did not collect information traveling over secure, password-protected WiFi networks.

So how did this happen? Quite simply, it was a mistake. In 2006 an engineer working on an experimental WiFi project wrote a piece of code that sampled all categories of publicly broadcast WiFi data. A year later, when our mobile team started a project to collect basic WiFi network data like SSID information and MAC addresses using Google’s Street View cars, they included that code in their software—although the project leaders did not want, and had no intention of using, payload data.

As soon as we became aware of this problem, we grounded our Street View cars and segregated the data on our network, which we then disconnected to make it inaccessible. We want to delete this data as soon as possible, and are currently reaching out to regulators in the relevant countries about how to quickly dispose of it.

Fair enough. But the following excerpt from the report doesn’t quite sit so well with me: “We are logging user traffic along with sufficient data to precisely triangulate their position at a given time, along with information about what they were doing.” To be more specific, the last portion about knowing “what they were doing” seems a bit peculiar. Why would Google need to know what they were doing? Seems irrelevant if you’re just mapping the location of networks, doesn’t it?

So how did Google spin this to the media? It said the data mining was “inadvertent” and that Google now has stricter privacy controls than in the past. Oh and the company hopes the release of the full report would allow them to “put this matter” in the rear view mirror.

Crazy, right? Or maybe not! Discuss.

Correction: April 28, 2012 9:46PM PT

An excerpt from the report has been added regarding the pre-approval of a document sent out by “Engineer Doe” to the Street View team that detailed the work being done and included the fact that Google would be collecting such data.

Read this article:
Google Releases Full Report On Street View Investigation, Finds That Staff Knew About Wi-Fi Sniffing

NVIDIA unleashes GeForce GTX 690 graphics card, loads it with dual Kepler GPUs, charges $1k

ImageWould you look at that? NVIDIA hinted it would be coming today, and it looks like the tease is living up to the hype. The company stormed into the weekend at its Shanghai Game Festival by unleashing its latest offering, the GeForce GTX 690 — and oh yeah, it’s packing two 28nm Kepler GPUs! Trumping the recently released GTX 680 as the “worlds fastest graphics card,” it’s loaded with a whopping 3,072 Cuda cores. The outer frame is made from trivalent chromium-plated aluminum, while you’ll find thixomolded magnesium alloy around the fan for vibration reduction and added cooling. Aiding in cooling even further, the unit also sports a dual vapor chamber and center-mounted fan. It’ll cost you a spendy $1,000 to pick up one of these puppies come May 3rd, and you’ll likely be tempted to double up — two can run together in SLI as an effective quad-core card. With that said, NVIDIA claims that a single 690 runs 4dB quieter and handles about twice the framerate as a duo of GTX 680s in SLI — impressive, but we’ll reserve judgement until we see it for ourselves. Check out the press release after the break if you’d like more information in the meantime (…and yes, it runs Crysis2 Ultra to be exact — at 57.8fps, according to NVIDIA).

[Thanks to everyone who sent this in]

Continue reading NVIDIA unleashes GeForce GTX 690 graphics card, loads it with dual Kepler GPUs, charges $1k

NVIDIA unleashes GeForce GTX 690 graphics card, loads it with dual Kepler GPUs, charges $1k originally appeared on Engadget on Sun, 29 Apr 2012 00:57:00 EDT. Please see our terms for use of feeds.

Permalink | | Email this | Comments

See more here:
NVIDIA unleashes GeForce GTX 690 graphics card, loads it with dual Kepler GPUs, charges $1k

Facebook 'Likes' Aren't Protected Speech

An anonymous reader writes “In what may win awards for the silliest-sounding lawsuit of the year, a case about whether Facebook ‘likes’ qualify for free speech protection under the First Amendment has ended in a decisive ‘no.’ In the run-up to an election for Sheriff, some of the incumbent’s employees made their support for the challenger known by ‘liking’ his page on Facebook. After the incumbent won re-election, the employees were terminated, supposedly because of budget concerns. The employees had taken a few other actions as well — bumper stickers and cookouts — but they couldn’t prove the Sheriff was aware of them. The judge thus ruled that ‘merely “liking” a Facebook page is insufficient speech to merit constitutional protection. In cases where courts have found that constitutional speech protections extended to Facebook posts, actual statements existed within the record.'”


Share on Google+

Read more of this story at Slashdot.

More:
Facebook 'Likes' Aren't Protected Speech