-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Libunbound openssl error - 0.11.0.0 release version #2411
Comments
This prevents DNSSEC verification, but it's apparently not done well in the first place anyway. This looks like an OpenSSL which was compiled with SHA1 (or a cmake bug which causes USE_SHA1 to be undefined when building unbound). |
Possibly some relevant information here.
https://www.unbound.net/pipermail/unbound-users/2016-January/004176.html |
(referencing #2133 for housekeeping) |
I am afraid that it does see to stop us syncing or even accessing the wallet at all. MY balance is 0.00000 at the moment.
|
Can you file new bugs separately please, or this is going to be really confusing. One of the txes in the pool seems to be corrupt. |
Might be fixed by #2996 |
Can someone who had that problem confirm whether this is fixed ? |
it's fixed for me (Ubuntu 16.04 LTS) 🙂 |
Thanks +resolved |
A few users have been reporting these "errors" on Linux 64-bit (using the latest release, Helium Hydra):
As far as I can tell, it doesn't inhibit them from syncing or using the daemon.
Source:
https://www.reddit.com/r/Monero/comments/6yprar/mandatory_upgrade_monero_01100_helium_hydra/dmpa8ab/
The text was updated successfully, but these errors were encountered: