Closed egyptianbman closed 5 years ago
@egyptianbman thanks for the bug report! Can you clarify, does the daemon shut down or stop, or is this just a "warning" ?
Hey @leto, it doesn't stop or shut down, just a warning but one I haven't seen on any other node before.
@egyptianbman can you tell us the output of hushd --version
? I think this error only happens on newer Hush versions
Hush Daemon version v2.0.0-21739aad7
In order to ensure you are adequately protecting your privacy when using Hush,
please see <https://github.com/MyHush/hush/blob/master/doc/security.md>.
Copyright (C) 2009-2018 The Bitcoin Core Developers
Copyright (C) 2015-2018 The Zcash Developers
Copyright (C) 2016-2018 The Hush Developers
This is experimental software.
Distributed under the MIT software license, see the accompanying file COPYING
or <http://www.opensource.org/licenses/mit-license.php>.
This product includes software developed by the OpenSSL Project for use in the
OpenSSL Toolkit <https://www.openssl.org/> and cryptographic software written
by Eric Young.
GIN recently enabled dpow and is seeing the same issues.
Seems to be triggered when invalid blocks are received from outdated peers
Ah, in that case it's more of a warning than an error/exception.
This warning happened when old non-updated Hush nodes try to talk to new dpow-enabled Hush nodes, and there was a printf() with an extra %d when logging this fact. It was not security-critical, but good to fix
Describe the issue
Random exception
Can you reliably reproduce the issue?
If so, please list the steps to reproduce below:
Expected behaviour
No exceptions
Actual behaviour + errors
I occasionally see the following:
The version of Hush you were using:
Run
hushd --version
to find outMachine specs: