Published on: 2015-10-08T05:14:50+00:00
James O'Beirne has confirmed a bug in the recently merged "obfuscation" patch for Bitcoin's CLevelDBWrapper. The bug involves obfuscating the content of the "chainstate" LevelDB by XOR'ing it against a random key. While CLevelDBWrapper's Read/Write methods handle most use cases, there is a question regarding whether iterating over the database should also be handled. In particular, it has been suggested that the obfuscation key should be applied during iteration in CCoinsViewDB::GetStats. James has filed a fix for the issue on GitHub at https://github.com/bitcoin/bitcoin/pull/6777. To prevent any future regressions, James will also be writing tests. Daniel, who reported the bug, expressed gratitude for the quick fix and had planned to submit a patch if the issue turned out to be an oversight. It is worth noting that Daniel's signature block includes links to his website, OpenPGP key, and Namecoin ID.The author of a message is seeking clarification about the recently merged "obfuscation" patch for Bitcoin's CLevelDBWrapper. The patch obfuscates the "chainstate" LevelDB by XOR'ing it with a random key. The author wonders if the obfuscation should also be applied during iteration over the database. Specifically, they question whether the obfuscation key should be applied before line 119 in txdb.cpp during iteration in CCoinsViewDB::GetStats. They are unsure if this was an oversight or if there is a specific reason why the obfuscation key does not need to be applied during iteration. The author is reaching out to the community for help before opening a Github ticket.
Updated on: 2023-08-01T16:34:18.258525+00:00