Google.ps domain was hacked • Hacker News Board

Re: Google.ps domain was hacked

#81

Post by [deleted] » Mon, Aug 26, 2013, 9:15 PM UTC

s_q_b wrote: post #43

biot wrote: post #30

... and thousands of HN readers get infected by a zero-day exploit. Maybe. If you're thinking of submitting a known compromised site to HN, consider instead submitting a third-party site which explains/documents the compromise. Ideally from a respected security research company. This has several benefits: 1. You're not subjecting HN readers to a site under the control of a malicious party who may have done more than…

I agree with your point, but 0-day exploits aren't tossed around like candy corn. They're multi-million dollar munitions.

[deleted]

Re: Google.ps domain was hacked

#82

Post by mobiplayer » Mon, Aug 26, 2013, 9:51 PM UTC

Being the Google bar on the screenshot in French and the name servers on a Moroccan hosting provider I think it's clear where these script kiddies are from :)

Re: Google.ps domain was hacked

#83

Post by mobiplayer » Mon, Aug 26, 2013, 9:52 PM UTC

mobiplayer wrote: post #82

Being the Google bar on the screenshot in French and the name servers on a Moroccan hosting provider I think it's clear where these script kiddies are from :)

P.S.: Not implying anything, just adding information. I've re-read my comment and it looks a bit wrong.

Re: Google.ps domain was hacked

#84

Post by packetslave » Mon, Aug 26, 2013, 10:32 PM UTC

ponyous wrote: post #50

dsl wrote: post #34

Earlier quoted context omitted.

Google's incident response team deals with far bigger issues on a daily basis. This is hardly more than a few kids playing around.

Care to elaborate?

Nice try, Mark Zuckerberg

Re: Google.ps domain was hacked

#85

Post by dsl » Mon, Aug 26, 2013, 10:37 PM UTC

kijeda wrote: post #55

dsl wrote: post #37

Earlier quoted context omitted.

This isn't a DNS issue, it's a SQL injection attack. ICANN needs to mandate stronger requirements for best practices with web based management UIs. Unfortunately they have little in the way of real control over ccTLDs. You'd be best served registering ccTLDs and redirecting them to your gTLD of choice (say, .com) and not trying to serve localized content from them.

ICANN is not in a position to mandate such requirements for ccTLDs as they are not empowered to. ccTLD governance differs from gTLDs in that each country code is managed and overseen locally within the country. This is why there is such a diversity in ccTLD policies. For better or worse this model of subsidiarity is what we have today.

Which is why I said

> Unfortunately they have little in the way of real control over ccTLDs.

Hopefully NTIA can empower ICANN (as the IANA operator) to better exercise security requirements against ccTLDs. Ultimately NTIA can pull the ccTLD from the root, which is a stick we could use increase the overall security of the internet, but I would prefer we find a carrot.

Re: Google.ps domain was hacked

#86

Post by smtddr » Mon, Aug 26, 2013, 10:49 PM UTC

hack_edu wrote: post #72

pearjuice wrote: post #65

Earlier quoted context omitted.

That is not what "hacked" means. If they had really hacked Google their servers and proxied all searches through a system of theirs without letting the users know it would not have been "apparent" yet Google was hacked in the correct sense of the definition. They were defaced which was directly apparent to users - not hacked. At all.

I'll repeat the crux of this discussion. There's no definition of 'hacked.' Welcome to the Internet.

if i stood in front of your house with a cellphone jammer, did i just hack your cellphone service provider?

Re: Google.ps domain was hacked

#87

Post by eksith » Mon, Aug 26, 2013, 11:27 PM UTC

tambourine_man wrote: post #52

http://i.imgur.com/BNspAdZ.jpg

Thank you.

I wish OP would have done the same with a comment. In fact, this should probably be standard procedure when submitting a link to a compromised site if it's not to a blog/news post about it.

Re: Google.ps domain was hacked

#88

Post by nuclear_eclipse » Tue, Aug 27, 2013, 1:01 AM UTC

omarchowdhury wrote: post #68

biot wrote: post #30

... and thousands of HN readers get infected by a zero-day exploit. Maybe. If you're thinking of submitting a known compromised site to HN, consider instead submitting a third-party site which explains/documents the compromise. Ideally from a respected security research company. This has several benefits: 1. You're not subjecting HN readers to a site under the control of a malicious party who may have done more than…

Now you've got me paranoid.

You don't know paranoia until you've worked in the network security industry for a government contractor....

Re: Google.ps domain was hacked

#89

Post by captn3m0 » Tue, Aug 27, 2013, 3:53 AM UTC

Using HTTPS Everywhere gave me a warning on visiting https://google.ps, Chrome blocked the url giving a warning on the HSTS/certificate pinning.

Re: Google.ps domain was hacked

#90

Post by mentat » Tue, Aug 27, 2013, 6:04 AM UTC

s_q_b wrote: post #43

biot wrote: post #30

... and thousands of HN readers get infected by a zero-day exploit. Maybe. If you're thinking of submitting a known compromised site to HN, consider instead submitting a third-party site which explains/documents the compromise. Ideally from a respected security research company. This has several benefits: 1. You're not subjecting HN readers to a site under the control of a malicious party who may have done more than…

I agree with your point, but 0-day exploits aren't tossed around like candy corn. They're multi-million dollar munitions.

There are tons of 0-days out there, maybe not in Chrome proper but in Java, in extensions, in flash... Multi-million is a huge exaggeration. I think market is 20k - 50k for many areas.