81–90 of 100 posts
... I find the choice of words funny. If he hadn't bothered to buy a domain he knew he would never be able to keep, there would be no ordeal!!!
In Ireland some one managed to redirect google.ie (The irish google search domain): http://technology.ie/google-ie-hijacked/ The ccTLD register (The IEDR) had a vulnerability in their management portal that was exploited (I believe it was an SQL injection if I recall correctly). The attacker changed the DNS servers to their own and then put an A name record pointing google.ie to their own server. The server just disp…
In Ireland some one managed to redirect google.ie (The irish google search domain): http://technology.ie/google-ie-hijacked/ The ccTLD register (The IEDR) had a vulnerability in their management portal that was exploited (I believe it was an SQL injection if I recall correctly). The attacker changed the DNS servers to their own and then put an A name record pointing google.ie to their own server. The server just disp…
'their'
Honest question. If he bought the domain from Google and the transaction went through, is that not technically a legitimate transaction and "cancelling" and refunding the money is essentially theft? How is that any different than walking in to someone's house and leaving them $20 for the TV you took? It seems to me that "oops, take-backs" Is not a legitimate enough justification to reverse a transaction under contrac…
Let's say you're selling a 10$ gift card on your website but through some bug/error it's now worth 1000$ (an easy mistake to make, just forget the decimal place). What if someone bought the 1000$ worth gift card for the original intended price of 10$? I'm sure you would invalidate that purchase and send them an email explaining that it was a mistake, and it would be perfectly within your rights to do so.
It goes both ways too, if a mistake is made that advantages the seller, they have to fix it.
finally. i like the idea someone can remove my last purchase and manipulate my account.
It wasn't a valid purchase. What would you expect to happen? Google.com, like the Brooklyn Bridge, isn't for sale.
Your comment implies that the sale should have gone through anyway, which is nonsensical. Otherwise we could have situations where I steal foo.bar from you (which you have registered with, say, NameCheap) by buying it through, say, GoDaddy, which is currently experiencing a similar bug that incorrectly marks your domain as available.
Honest question. If he bought the domain from Google and the transaction went through, is that not technically a legitimate transaction and "cancelling" and refunding the money is essentially theft? How is that any different than walking in to someone's house and leaving them $20 for the TV you took? It seems to me that "oops, take-backs" Is not a legitimate enough justification to reverse a transaction under contrac…
Mistakes can and do happen in business all the time, because businesses are composed of people and people aren't perfect. The solution is to deal with mistakes in whatever is the most sane way.
On the 20.09, I received a totally legit invoice from invoice@google.com (99.99€ Candyclub - Bag of Gems). The sender is invoice@google.com, but no names, no other personal information. I thought it was somewhat strange, and reported it, but no answer.
It's extemely simple to fake the sender of email. That's what probably happened.
Earlier quoted context omitted.
How exactly would that work. modify an instance of bind and check if the client is requesting to resolve 'google.com'? If true, then respond with the rouge IP? First we must make sure the client machine is set up to use our name servers, the ones we have control over.
Never use a rouge IP. They're red for a reason, man.