Topic: Question about Verifying Database entries (Read 539 times)
To do what your saying, could be done in mysql, hash the username, and balance together, then have a very secure, and long salt, to make sure nothing can be changed.
So I'm working on a service that uses a mysql database to keep track of user balances. I've done about as much as I and my developer knows to keep the Bitcoind safe from attackers- mostly a cold wallet to just form the basis of the protection and limit interest in trying to steal it.
There still lingers in my mind though the silent threat of someone compromising the system and managing to every so slightly manipulate the database so as to slowly over time bleed dry the system.
Any ideas how to protect a dabatase or to prevent it's manipulation? A way to have verifiable records?
One idea I had thought about was using a nosql database like MondoDB, where every time a record was made the hash of all it's contents was saved in another database so that records could be verified.
Any other ideas? Any places I should start looking?
There still lingers in my mind though the silent threat of someone compromising the system and managing to every so slightly manipulate the database so as to slowly over time bleed dry the system.
Any ideas how to protect a dabatase or to prevent it's manipulation? A way to have verifiable records?
One idea I had thought about was using a nosql database like MondoDB, where every time a record was made the hash of all it's contents was saved in another database so that records could be verified.
Any other ideas? Any places I should start looking?
Jump to: