Live data from Hacker News

Google.ps domain was hacked

google.ps

51–60 of 92 posts

Re: Google.ps domain was hacked

#51
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…

You're not subjecting HN readers to a site under the control of a malicious party who may have done more than just deface it.

I don't see any malicious action here.

Re: Google.ps domain was hacked

#53

Please change the title to "Google Palestine defaced" or "Google DNS entries maliciously changed". Google Palestine was/is not hacked.

Yes it was. Let's not quibble.

No it was not. It implies something under Google their control was compromised which was not the case.

Re: Google.ps domain was hacked

#54
post #41

The page also tries to load a mp3 file using Real Player. Sounds bad... Is that some known exploit? Real Player is so rear this days, so at list it wouldn't be my first choice if you only wanted to play a song.

The mp3 is "Hard", by Rihanna. Doesn't seem to have any exploits attempted (it plays fine in mplayer, with no funny business).

Re: Google.ps domain was hacked

#55
post #37
post #31

Aren't we seeing a lot of DNS based attacks in the recent past? I remember .pk TLD was hacked not too long ago. Considering that most of the big sites run local variants of their services using these TLDs is it fair to assume that one of these next ones could be of the phishing kind? What's the best thing to do - always use the .com hoping that it is safer?

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.

Re: Google.ps domain was hacked

#56
post #51
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…

You're not subjecting HN readers to a site under the control of a malicious party who may have done more than just deface it. I don't see any malicious action here.

How is defacing a page not "malicious"?

Re: Google.ps domain was hacked

#58

Earlier quoted context omitted.

Yes it was. Let's not quibble.

No it was not. It implies something under Google their control was compromised which was not the case.

Really, it implies any attack or breach that is apparent to users. This is very apparent.

Re: Google.ps domain was hacked

#60

Good job, butthurt nationalist losers ;-).

And if this were done by jews being oppressed somewhere, your reaction would be the same?

Not that you'll take this advice, but I'd really recommend spending a little time thinking about what if you were born with a different last name.

Would you be a butthurt loser then, by dint of that last name?

Post reply on HN