Risk
2/12/2010
03:01 PM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Google Buzz Gets Privacy Patch

Responding to complaints, the company has enhanced the privacy options for Buzz users.

Google on Thursday declared Buzz a success while simultaneously announcing several changes to enhance the privacy of Buzz users amid a growing chorus of complaints.

Tens of millions of people have experimented with Buzz, the company said, resulting in over 9 million posts and comments. It also said that it was seeing 200 Buzz posts per minute coming in from mobile phones.

That's a drop in the bucket compared to the 135.5 billion spam messages per day that McAfee reported as an average in 2009, but Buzz is just getting started. Whether Buzz has a future may depend on how it addresses user privacy concerns, which have already led some users to disable the service.

Buzz is Google's second attempt to reinvent e-mail, its first being Google Wave, the promising but unreleased marriage of e-mail, instant messaging and collaboration.

Gmail users who enable Buzz can share photos, videos and status updates with a ready-made social network, their Gmail contacts. The trouble is that Buzz's proclivity to share often defies user expectations by making information like e-mail addresses, contact names, and social connections publicly accessible.

Facebook has been wrestling with privacy problems of this sort for years and now Google has stepped into the ring. The problem for Google, or any social network, is that people have differing privacy expectations and what one user accepts another may find invasive. Thus any default setting that isn't completely private is bound to upset some users. Privacy also has a different impact on different people. For some, a breach of privacy may mean embarrassment; for others, it can mean physical harm or legal jeopardy.

Some of those complaining online about Buzz have claimed that the service has exposed their contact information to people who have threatened them or outed the confidential sources of journalists.

On Thursday, Todd Jackson, product manager for Buzz, acknowledged that Google had heard from concerned users who believed their contacts were being made public without their knowledge and who were upset that they had too little control over who could follow them.

Jackson said that in response to feedback, Google has made the option to not display follower information on public profiles more visible. The company has also made it possible to block followers who have not created a Google Profile and has made information about followers more clear.

While this may restore user trust in Buzz for some, Mike Geide, a senior security researcher with Zscaler who described in a blog post how Buzz could be misused by spammers, says that the service still could be misused. "These improvements could help to prevent spammers from following users who limit their ability to be followed -- in other words, it is still up to users to policy their profile," he said in an e-mail. "[But] E-mail addresses are still visible for those users that your Gmail account has corresponded with, so the e-mail validation problem still exists for Buzz."

Google maintains that its spam detection systems would be likely foil such spamming efforts.

"Google works hard to fight spam, and in fact, the anti-spam technology in Gmail is one of the key reasons why people choose to use Gmail in the first place," a company spokesperson said in an e-mail. "Similarly, we are focused on eliminating spam from Google Buzz as much as possible. A random number is associated with the URL of your public Google Profile by default for extra privacy, as opposed to a username. Additionally, our spam-fighting algorithms help detect and stop the types of automated harvesting methods that are discussed theoretically in the [Zscaler] report. We have not seen any evidence of such methods being used against Gmail users through Google Buzz."

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
20 Questions to Ask Yourself before Giving a Security Conference Talk
Joshua Goldfarb, Co-founder & Chief Product Officer, IDDRA,  10/16/2017
Printers: The Weak Link in Enterprise Security
Kelly Sheridan, Associate Editor, Dark Reading,  10/16/2017
Hyatt Hit With Another Credit Card Breach
Dark Reading Staff 10/13/2017
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Security Vulnerabilities: The Next Wave
Just when you thought it was safe, researchers have unveiled a new round of IT security flaws. Is your enterprise ready?
Flash Poll
The State of Ransomware
The State of Ransomware
Ransomware has become one of the most prevalent new cybersecurity threats faced by today's enterprises. This new report from Dark Reading includes feedback from IT and IT security professionals about their organization's ransomware experiences, defense plans, and malware challenges. Find out what they had to say!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.