Risk
1/31/2008
06:19 AM
50%
50%

Stopping Google Blog Spam

Removing spam from your Google blog - in seven 'easy' steps

4:19 PM -- Today is no different from yesterday or the day before: Nope, it’s just another day that Google has made things a little worse for Yours Truly. Full disclosure: I don’t actually use Google anymore. I’ve long since realized that Yahoo’s Overture actually has better results than Google and a much bigger index, which helps when searching for esoteric strings. So the only time I find myself on the search giant is when I’m bug hunting or debugging someone else’s problem.

That brings me to my first Google rant of the day. My girlfriend emailed me today, asking if Google was down. Clickity clickity... Nope, looks good to me. But it appeared that every time she went to the page, she was getting something that looked like this:

Figure 1:

It appears that someone at her office did something that caused Google to basically shut down "search" for everyone in the office. Most Internet users would be helpless without Google, but thankfully my girlfriend knows the ways of Yahoo, so she continued about her day. But there are still hundreds of people at her company left without Google search for as yet-unknown reasons.

Google provides no way to rectify the situation, so guys like me end up playing tech support for them. I tell people to use another search engine. (I’m probably not the best Google tech support person, am I? I’m guessing they aren’t banking on me telling hundreds of people at a time to stay off their site.)

After the drama, I look through Technorati and find a spammer on Blogspot. (See Attackers Abuse Google Blogger .) The spammer has decided to take my content and re-post it as its own. That wouldn’t be a problem, except that they’ve posted it to the Google-owned Blogspot. Google isn’t just a search company -- it's also an advertising company, and it often hosts security hole-ridden beta applications and spam. You’d think it would be easy enough to tell Google to cease and desist with the spam, but no. That would be too easy and responsible of Google. So here’s the easy seven-step process for removing spammer’s content from Blogspot:

  1. Identify the content on Blogspot that is infringing on your copyright. (So far so good.)

  2. Show where your original content lives and the date that you posted it. (Easy enough.)

  3. Provide contact info. (Not sure why that’s necessary to remove a spammer, but okay...)

  4. Include the statement “I have a good faith belief that use of the copyrighted material described above on the allegedly infringing web pages is not authorized by the copyright owner, its agent, or the law.” (Um... okay?)

  5. Include the statement “I swear, under penalty of perjury, that the information in the notification is accurate and that I am the copyright owner or am authorized to act on behalf of the owner of an exclusive right that is allegedly infringed.” (Why didn’t Google just add those two sentences together and make them one bullet?)

  6. Sign the paper. (Yes, PAPER... Right back to 1980 we go!)

  7. Send or fax the paper to Google. (I could have sworn Google was an Internet company!)

Google has actually made it harder to stop a spammer than it is to be a spammer. And people who have been infringed upon actually have to spend money -- long-distance phone call or postage -- to stop spammers on Google’s own domain. This by no means guarantees that it will be removed in a timely manner, either. Isn’t it time we demand Google fix its own problems rather than placing the burden on everyone else?

At a minimum, let’s demand that Google’s legal department start using email.

– RSnake is a red-blooded lumberjack whose rants can also be found at Ha.ckers and F*the.net. Special to Dark Reading

  • Google (Nasdaq: GOOG)

    Comment  | 
    Print  | 
    More Insights
  • Register for Dark Reading Newsletters
    White Papers
    Cartoon
    Current Issue
    Dark Reading Tech Digest, Dec. 19, 2014
    Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
    Flash Poll
    Video
    Slideshows
    Twitter Feed
    Dark Reading - Bug Report
    Bug Report
    Enterprise Vulnerabilities
    From DHS/US-CERT's National Vulnerability Database
    CVE-2004-2771
    Published: 2014-12-24
    The expand function in fio.c in Heirloom mailx 12.5 and earlier and BSD mailx 8.1.2 and earlier allows remote attackers to execute arbitrary commands via shell metacharacters in an email address.

    CVE-2014-3569
    Published: 2014-12-24
    The ssl23_get_client_hello function in s23_srvr.c in OpenSSL 1.0.1j does not properly handle attempts to use unsupported protocols, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via an unexpected handshake, as demonstrated by an SSLv3 handshak...

    CVE-2014-4322
    Published: 2014-12-24
    drivers/misc/qseecom.c in the QSEECOM driver for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, does not validate certain offset, length, and base values within an ioctl call, which allows attackers to gain privileges or c...

    CVE-2014-6132
    Published: 2014-12-24
    Cross-site scripting (XSS) vulnerability in the Web UI in IBM WebSphere Service Registry and Repository (WSRR) 6.3 through 6.3.0.5, 7.0.x through 7.0.0.5, 7.5.x through 7.5.0.4, 8.0.x before 8.0.0.3, and 8.5.x before 8.5.0.1 allows remote authenticated users to inject arbitrary web script or HTML vi...

    CVE-2014-6153
    Published: 2014-12-24
    The Web UI in IBM WebSphere Service Registry and Repository (WSRR) 6.3.x through 6.3.0.5, 7.0.x through 7.0.0.5, 7.5.x through 7.5.0.4, 8.0.x before 8.0.0.3, and 8.5.x before 8.5.0.1 does not set the secure flag for a cookie in an https session, which makes it easier for remote attackers to capture ...

    Best of the Web
    Dark Reading Radio
    Archived Dark Reading Radio
    Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.