Author

Topic: Blockchain.info - Bitcoin Block explorer & Currency Statistics - page 152. (Read 482395 times)

sr. member
Activity: 378
Merit: 250
"Yes I am a pirate, 200 years too late."
http://blockchain.info/pools

Why are to big unknown hashing sources separated?
Is one of them only one miner/pool?

Also, does anybody knows more about what's happening?
I was used to see known pools dominating the market.


He just said pool stats would be messed up for a little while.
legendary
Activity: 1372
Merit: 1002
http://blockchain.info/pools

Why are to big unknown hashing sources separated?
Is one of them only one miner/pool?

Also, does anybody knows more about what's happening?
I was used to see known pools dominating the market.
sr. member
Activity: 311
Merit: 250
Bitcoin.se site owner
Let's remember that it is there to prevent someone who has your password gaining access. But if they have the password you'll disable two factor anyway.

The secret phrase is not the same thing as the password. It is a separate phrase that you can optionally set under Account Details.
hero member
Activity: 504
Merit: 502
Google Authenticator support added:

https://blockchain.info/wallet/google-authenticator

It's pretty easy to use, I prefer it to yuibikey.

Looks good.. except...

Quote
No problem, simply contact us with wallet identifier, secret phrase and any other information you can provide and we will disable two factor authentication.

It seems to me that this makes two factor authentication pointless.

Let's remember that it is there to prevent someone who has your password gaining access. But if they have the password you'll disable two factor anyway.
hero member
Activity: 737
Merit: 500
Sorry to hear about the recent struggles.

I noticed that transaction timestamps are not accurate for some transactions.  I assume this is related to the downtime.  

For example, these three transactions appear to be at the same time (10:55:56 UTC) which I assume is the time that the servers came back up:

http://blockchain.info/tx/ee110ffd1d9ae7147694ce541321d21f060cacf44ed88bebc80c483fd00c5684
http://blockchain.info/tx/d45c56dd94bc644c3f15a45c5760516353a0c345043dc46ac4733e086e4c82c0
http://blockchain.info/tx/dd16af39e22ec4d6cd3653000b134ca979df55f4f91130066ba39a25514a3d23

I assume you aren't planning to backload more accurate timestamps (e.g. the time from the block header) and that I should work around this myself?  

hero member
Activity: 910
Merit: 1005
Google Authenticator support added:

https://blockchain.info/wallet/google-authenticator

It's pretty easy to use, I prefer it to yuibikey.
hero member
Activity: 910
Merit: 1005
Transactions per Day is going high - thats fine - or do you count all that payouts from p2pool-blocks to the users as one Transaction pro Reciver?

P2Pool payouts are counted as one transactions. I'm pleased to see it increasingly a lot lately, if it carries on this rate we will soon back at June levels. Good indicator imo.
full member
Activity: 131
Merit: 100
Transactions per Day is going high - thats fine - or do you count all that payouts from p2pool-blocks to the users as one Transaction pro Reciver?
legendary
Activity: 2184
Merit: 1056
Affordable Physical Bitcoins - Denarium.com
Ok were back. It started as what I thought was a bad firewall rule, but was actually a more serious failure of one machine. But everything is back online now and there has been absolutely no dataloss.

Again apologies for the downtime. Pool stats will be screwed up for a while.

Google authenticator support coming later today.
+1

Google auth support sounds really good! I use it with my Lastpass and I love it.
hero member
Activity: 910
Merit: 1005
Ok were back. It started as what I thought was a bad firewall rule, but was actually a more serious failure of one machine. But everything is back online now and there has been absolutely no dataloss.

Again apologies for the downtime. Pool stats will be screwed up for a while.

Google authenticator support coming later today.
hero member
Activity: 910
Merit: 1005
The server is ready to go again, but unfortunately i'm not going to make it back to the datacenter tonight. I could probably get the site online again with two servers, but then I'd just have to undo the changes in the morning + It's valentines night and i've got none optional dinner plans.

9:00 AM GMT tomorrow it will be back up. Really sorry for any My Wallet users who cannot access their account, if you are in dire need to make a transaction and don't have a backup let me know your wallet identifier and i'll send you a backup and instructions on how to get your keys into bitcoind.
full member
Activity: 130
Merit: 100
that sucks bro ..


well god speed
hero member
Activity: 910
Merit: 1005
The engineer told me that machine 3 wouldn't boot after being reset so I drove down to pick it up. I've got it at home now and it boots fine but there is something not quite right with it. When I enable the firewall it locks up, even though the rules are fine. I am going to reinstall the OS then take it back down.

Just to be clear there is no data loss, but this server acts as the "Management node" for the MySQL cluster and it site won't start without it.
sr. member
Activity: 311
Merit: 250
Bitcoin.se site owner
How's it going with the site, piuk?
hero member
Activity: 714
Merit: 500
Be careful.
Be safe.
full member
Activity: 127
Merit: 100
or iptables -F in order to rebuild the rulelist... without resetting the default DROP policy  Roll Eyes
legendary
Activity: 1750
Merit: 1007
Having a few problems with the Site this morning. In light of the recent hackings I was changing all passwords and closing any none essential ports - In doing so I've managed to lock myself out one of the servers.  I'm waiting for someone at the colo to restart it now, should be back up in an hour or so.

Edit: Engineer has confirmed he is on his way, should be approx ~20 mins.

Ah, the goold ole' 'iptables -A INPUT -p tcp --dport 22 -j DROP' going in before allowing your own IP full access ;p
hero member
Activity: 504
Merit: 502
Having a few problems with the Site this morning. In light of the recent hackings I was changing all passwords and closing any none essential ports - In doing so I've managed to lock myself out one of the servers.

Now that's what I call proactive security. ;-)
hero member
Activity: 910
Merit: 1005
Having a few problems with the Site this morning. In light of the recent hackings I was changing all passwords and closing any none essential ports - In doing so I've managed to lock myself out one of the servers.  I'm waiting for someone at the colo to restart it now, should be back up in an hour or so.

Edit: Engineer has confirmed he is on his way, should be approx ~20 mins.

Edit 2: The engineer at the datacenter said machine 3 wouldn't boot after being reset. I drove down to pick it up and am having a look at it now. Appears to boot fine, disk repair says everything is ok. However when i enable the firewall everything locks up.
hero member
Activity: 910
Merit: 1005
This looks pretty nifty. I noticed on that BTCServ hack that the small part gets spent twice to merge into a 40 BTC address. It would be useful to know what addresses payments get combined with as that may give clues about wallet (like a "back-link" on an address). I have no idea how it could be fit in a diagram because it would get "hairy" fast.

My hypothesis is that the coins change hands at the 40 BTC merge as the ip addresses switch from Germany to U.S. Maybe you could hover over a node to show any new inputs. Also the "Purity" of the coins (i.e. how much they have been mixed with the other transactions) could be represented by the thickness of the line.

So, that means the hacker either is close topologically by default or has added manually BTCServ IP as a peer? If the hacker is manually relaying thru BTCServ that's a bit like rubbing salt in a wound! Or another interpretation is that it's still controlled by BTCServ, though obviously not provably.

Or maybe the attacker sent some change back to BTCServe for some reason. I guess no matter how good future tools like this get it will still be almost impossible to prove anything.
Jump to: