News for hackers. Stuff that matters.
Re:Coinbase Merchant Data Leak? by pathy on Friday April 05, 2013 @09:02AM (#5498099)
Why are the checkout pages even public? No robots.txt, a lot of private information listed and public.

Shameful. I know little about web development but this seems rather obvious, even to me.

Re:Coinbase Merchant Data Leak? by clicks on Friday April 05, 2013 @09:10AM (#5498146)
https://encrypted.google.com/search?q=site:https://coinbase....

Phone no., names, addresses, e-mails, etc. all out. This is indeed pretty bad. A lot of people I know who use BTC use it foremost for privacy reasons, it is tremendously ironic how this has worked out.

Re:Coinbase Merchant Data Leak? by thefreeman on Friday April 05, 2013 @09:12AM (#5498155)
If you are using BTC for privacy, then using a third party hosted wallet is not a very good plan.
Re:Coinbase Merchant Data Leak? by johnyzee on Friday April 05, 2013 @09:56AM (#5498413)
Presumably you can take your bitcoins out whenever you want if you need to use them anonymously.
Re:Coinbase Merchant Data Leak? by smallegan on Friday April 05, 2013 @10:28AM (#5498605)
This is seller information to tell you who you are paying. There is no data leak here.
Re:Coinbase Merchant Data Leak? by Zirro on Friday April 05, 2013 @09:08AM (#5498136)
Using a robots.txt-file to hide data that shouldn't be public in the first place is a rather bad idea. Because the robots.txt itself is public, it actually highlights the location of the "private" data.
Re:Coinbase Merchant Data Leak? by benmanns on Friday April 05, 2013 @09:25AM (#5498228)
And, Google had to find a link to this content somehow, which means it's publicly accessible from some Coinbase page.
Re:Coinbase Merchant Data Leak? by manojlds on Friday April 05, 2013 @10:03AM (#5498457)
That is what I am wondering. Here I am building a web site and wondering how to make Google index sites behind authentication and such, and here is a site that has got everything indexed.
Re:Coinbase Merchant Data Leak? by benmanns on Friday April 05, 2013 @04:34PM (#5500892)
After reading Coinbase's response, it seems that the pages were not linked to by Coinbase, but by users posting links to their checkout page on the Internet.
Re:Coinbase Merchant Data Leak? by ntumlin on Friday April 05, 2013 @09:31AM (#5498263)
What's a good alternative to robots.txt?
Re:Coinbase Merchant Data Leak? by espo on Friday April 05, 2013 @09:38AM (#5498309)
Proper access control on your web site.
Re:Coinbase Merchant Data Leak? by Cthulhu_ on Friday April 05, 2013 @09:57AM (#5498418)
Simply not showing the transaction if you're not logged in and not the user belonging to the transaction?
Re:Coinbase Merchant Data Leak? by enoptix on Friday April 05, 2013 @09:58AM (#5498420)
You can also specify a meta robots tag inside the page HTML. If you want to block a lot of pages, your best bet would be to add it to your master layout or template. You get the same effect of blocking on robots.txt but without exposing a list of blocked pages.

The downside is that Google will still crawl the page and use your bandwidth, but the page won't be indexed.

Re:Coinbase Merchant Data Leak? by JimWestergren on Friday April 05, 2013 @11:25AM (#5498953)
I would suggest both these two: Check the user agent for bots and if it is a bot send a 404 header and exit before page needs to load. Also add a meta noindex just in case. Robots.txt DOES NOT prevent indexing, just crawling.
Re:Coinbase Merchant Data Leak? by dpcx on Friday April 05, 2013 @09:38AM (#5498302)
Blocking access to googlebot for those pages is the easiest. But robots.txt would work, if you just did

Ignore /checkouts/