Risk
2/17/2010
04:40 PM
Connect Directly
LinkedIn
Twitter
Google+
RSS
E-Mail
50%
50%

Google Buzz Brings Complaint From Canada

The country's Privacy Commissioner wants Google to explain how its changes to Buzz will address privacy concerns.

Canada's Privacy Commissioner on Wednesday challenged Google to clarify how it has addressed the privacy issued raised by the launch last week of the company's Buzz social networking service and chided the company for failing to consult her office prior to the product's launch.

"We have seen a storm of protest and outrage over alleged privacy violations and my Office also has questions about how Google Buzz has met the requirements of privacy law in Canada," Commissioner Jennifer Stoddart said in a statement.

Google says that it has already talked to Stoddart about Buzz and the changes it has made to the service. "We're always happy to hear from privacy commissioners in Canada and in other countries," a company spokesperson said in an e-mailed statement. "We regularly brief them on new products and features either before or just following launch, both as a courtesy to them and as a way to get valuable feedback on our products."

Google launched Buzz as a way to turn Gmail into a social network. Aware that some of the beta testers for Google Wave, the company's unreleased real-time social messaging platform, don't use the service much because of the absence of an existing social network, Google's Gmail team wanted to jump-start the lengthy process of building network connections by treating existing e-mail contacts as publicly viewable social networking friends. It was a decision that backfired.

In response to what Stoddart characterizes as "a storm of protest and outrage," Google twice changed the way Buzz works to accommodate privacy expectations.

Though Google's swift response shows that the company learned something from Facebook's foot-dragging following the controversy over its discontinued Beacon service, the changes in Buzz were nonetheless insufficient to satisfy critics of the company's privacy practices.

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6117
Published: 2014-07-11
Dahua DVR 2.608.0000.0 and 2.608.GV00.0 allows remote attackers to bypass authentication and obtain sensitive information including user credentials, change user passwords, clear log files, and perform other actions via a request to TCP port 37777.

CVE-2014-0174
Published: 2014-07-11
Cumin (aka MRG Management Console), as used in Red Hat Enterprise MRG 2.5, does not include the HTTPOnly flag in a Set-Cookie header for the session cookie, which makes it easier for remote attackers to obtain potentially sensitive information via script access to this cookie.

CVE-2014-3485
Published: 2014-07-11
The REST API in the ovirt-engine in oVirt, as used in Red Hat Enterprise Virtualization (rhevm) 3.4, allows remote authenticated users to read arbitrary files and have other unspecified impact via unknown vectors, related to an XML External Entity (XXE) issue.

CVE-2014-3499
Published: 2014-07-11
Docker 1.0.0 uses world-readable and world-writable permissions on the management socket, which allows local users to gain privileges via unspecified vectors.

CVE-2014-3503
Published: 2014-07-11
Apache Syncope 1.1.x before 1.1.8 uses weak random values to generate passwords, which makes it easier for remote attackers to guess the password via a brute force attack.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Marilyn Cohodas and her guests look at the evolving nature of the relationship between CIO and CSO.