>> (p.1)
    Author Topic: Coinsmack.com is hosted on Linode  (Read 1641 times)
    PrintCoins (OP)
    Hero Member
    *****
    Offline Offline

    Activity: 533
    Merit: 501


    View Profile
    March 02, 2012, 08:53:47 PM
     #1

    Some people today have faced some serious financial pain, and I have the utmost sympathy for  them, and respect that those who run services on linode that have been stolen from are eating the costs themselves.

    In the most non-gloating way that I can say this: I hosted a bitcoin service on linode and when I heard the news of the hack, I was completely unconcerned.

    Now, granted coinsmack's losses could have been covered by the change floating around in some people's couches. But even if the service was handling thousands of bitcoins, I still would be fine hosted on linode even if someone roots me.

    The reason why that is the case is that I don't run bitcoind on web servers. I consider it just a matter of time for a web server to be compromised, as there are just so many vectors of attack.

    So the way I set it up is that I generated 10000 keypairs on a local machine behind a firewall and with no other services turned on. It runs bitcoind with local rcp calls only. The public addresses are copied up to the webserver, and the webserver uses blockexplorer to check balances. Based upon the logic of the site as far as what needs to be paid out to what addresses, an admin page is generated that contains the data that is fed into the local bitcoind to handle the transactions (it is really all handled in just one massive transaction).

    This is manually initiated, so my monkey brain can take a quick scan of things and make sure things look alright before pressing the big red shiny button. Where the money goes and how much goes where is still determined by the webserver, but the transaction only happens outside of the webserver and by a manual process.

    Some people have asked why bitcoind on the hacked sites was not encrypted. This would indeed have saved them in this case, but if the site was hacked in another way where the server stayed online, and bitcoind had already decrypted the wallet so it could take transactions, that would still have resulted in the same loses.

    Trusting a webserver to store your wallet is a dangerous thing as is shown time and time again.

Page 1
Viewing Page: 1