Warning: OpenSSL Consensus Bug

cassini
Posts: 326
Joined: Sun May 26, 2013 6:36 pm

Re: Warning: OpenSSL Consensus Bug

Post by cassini » Fri Jul 31, 2015 3:13 pm

DrHaribo wrote:Any hints on how to build a 32-bit statically linked Namecoin Core binary to run on a 64-bit Linux?
The first two answers in http://stackoverflow.com/a/17748092/5099450 give a good explanation.
DrHaribo wrote:Btw, with Discus Fish at 67% hashpower, what are they mining with? 32-bit Namecoin Core?
They've used 64-bit Namecoin Core for the last few months. Yesterday we asked them to switch to 32-bit Namecoin Core. No feedback so far.

josephbisch
Posts: 69
Joined: Sun Nov 23, 2014 3:34 pm
os: linux

Re: Warning: OpenSSL Consensus Bug

Post by josephbisch » Fri Jul 31, 2015 6:53 pm

cassini wrote:
DrHaribo wrote:Any hints on how to build a 32-bit statically linked Namecoin Core binary to run on a 64-bit Linux?
The first two answers in http://stackoverflow.com/a/17748092/5099450 give a good explanation.
I may not have made it clear when I posted that SO answer, but it just builds 32-bit software on 64-bit Linux. It won't necessarily make the resulting binary be statically linked (unless that is the default for that software). What is it that you want specifically when you say statically linked? There is -static-libgcc or -static-libstdc++ that will statically link those respective libraries statically. I'm guessing you want -static instead, which will link all libraries statically. So you add -static to LDFLAGS like the following:

Code: Select all

./configure --host=i686-linux-gnu "CFLAGS=-m32" "CXXFLAGS=-m32" "LDFLAGS=-m32 -static"
I haven't actually tried building Namecoin Core statically, but that should work.

DrHaribo
Posts: 13
Joined: Wed Nov 14, 2012 9:37 pm
Contact:

Re: Warning: OpenSSL Consensus Bug

Post by DrHaribo » Fri Jul 31, 2015 9:32 pm

Having problems installing both 64 bit and 32 bit versions of some dependencies. Tried instead to compile a statically linked binary on a 32-bit Linux , but not having any success. ldd still shows dynamically linked libs. I tried the options you mentioned, among others.
▶▶▶ Bitminter.com - Your trusted mining pool since 2011.

biolizard89
Posts: 1932
Joined: Tue Jun 05, 2012 6:25 am
os: linux

Re: Warning: OpenSSL Consensus Bug

Post by biolizard89 » Sat Aug 01, 2015 11:28 am

Hello miners,

Here is a 32-bit Linux build of Namecoin Core:

https://drive.google.com/file/d/0B5Pa_I ... RVU1U/view

The SHA256 hash from Gitian:

1ba336184427b2ab297140967039faea73e352757651f389aef820d3a80abcdf build/out/namecoin-0.11.99-linux32.tar.gz

Since this was built with Gitian, it is statically linked and reproducible. The binary was posted by Joseph Bisch, and the hash was reproduced by Joseph Bisch and midnightmagic. Gitian was run like this:

./bin/gbuild --commit namecoin=9d1431453160a51b1eac18fe27d6840391cae3ec ../namecore/contrib/gitian-descriptors/gitian-linux.yml

Signatures from midnightmagic:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

1ba336184427b2ab297140967039faea73e352757651f389aef820d3a80abcdf namecoin-0.11.99-linux32.tar.gz
6f4c7d7dfd315470d4854b23498f5fe4b23edf4fbaf47af132f8a144b5908c80 namecoin-0.11.99-linux64.tar.gz
776b6aae6791c0a9b5b43a8cda8e6c50966a8dc6d07783cf7aeb8d96c2646830 src/namecoin-0.11.99.tar.gz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQQcBAEBAgAGBQJVvJLeAAoJECjfJyTyQdjupFkgAIGFrwQlNqJ13s/s2os7p6Gp
Mnb4tS13/ZupWvYWU1uNwbdbSzy4I3WgbkNgCePVJJK2jovcJiLrxnen4iRgHc7P
kZ3EBw2IZ0l5fV6r0Kp0u8J8PliUHmR1Q5D+/kvJUzO3wD16v66+dejZEiXkPMdl
SpdOxAzklJE6ASfqMS+LUTBy+beMd9T/vFza1LjqHbidGAQu/E3K6HCzhosSh/IX
kVEhe6HYqsl/BPQ3Pw+0xfx6KriU565lE4k6mGv3RSZlo1NYUwfltIdhBOLZ5qrR
7fH0M9VS7yRAwxUOfhBcvHdcucZ7kyuEKKD354y1aTrAvSJcXmcSqdkTZDOHfqZT
XNPMHVKWrU/LksPaWo8KwygC9ty0Vy8UMnL2v6+ihidcfX6G3BjNRuiwZNSBB6QO
VeX9NkIszKuq9Zd+uYXzlOi93dSHH04qw1ypmU46wBQd7ECn7Ct4BYT0CwyTISAu
82uUiTqNgki8Iy8vPb7EOd4E4RWadxJbmIK+YOxXCFznfeidjCPGlWHVM6Hf2WET
SQH8c6YatqaeM0Exy6amnJNle8B8aZtnYZZBTF3qAxYyfY8upzuRnDVaoZYUTrS0
pVNkDDVWZtStJrcvQeKtikwRAiVZyXnqJRCKioPt0DqRLhUcM/eas2/PTFiUQGnf
CCmGNoyiQ8q7WEuY6TuqBQn/03oey9GP+kfv+6PvgeoZeJXBacNvfdjrjdVqRdYa
7QcU/4EzdhXZHE9eoynGA3hhoGrDUl15tr/qbJQDU1hV/jGZIa+8LTZxJRN40WCR
uzQ+JNta1lFlmfg/Snn7mTd6CLpJveq8AcvQgcvGhZcWO/hDLORX3/EhcSVt/e9X
bzShIwYZ09CsUT4FPBZKiJT3RGvS7Hlk95Uk+hN/C+W+TVV7Qzx7Bef4rQiez4Ml
cTqFktAB3mztND6B8D21XaI884xjeUvaTooHC266ZzUJIgDdBhdBUKXLPE6ym25z
IlGvH/cbLSA9EX+b0R5TH70/R6J79nwykeSC3gNPL4q3S+h4PP1xPbTeRYgNyj0v
Zb83I6WMxfQgu1fZ1/MGOX2L2PJzMz0fzqZ3KM6I3MaKRXLPLhDcdJrmlTDHxc0O
LY72Z/EDlbyc6CVDb+ivwh2zPMEKrzpo2JPfgP/EZ0OszgWrpma2z6DGxAM6G3T5
UYl1hn//nGojR75vop1vwDAsErCn19a5rmNZtjO7p2NYgQ7E795l+kAE/enlQX8h
G6M9N7bhuRntApQ2fZLRWqK5ICL4YP2infIfMR+ai+/f4j5eEVAVCqKGehDZ8wuy
IUX1YdGbcJHjdZZx6wCHVE2FOL6ksb2AZZc5NEaO7aW9ByamueXuEwz3qBQ8B2U=
=SZjX
-----END PGP SIGNATURE-----

Joseph did not provide gsign signatures.

Be sure you verify the SHA256 hash, since we don't have any control over Google Drive's server.

To make this work on a 64-bit Debian Jessie installation, you need to do the following:

Code: Select all

sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install libc6:i386
After that, namecoind should run properly. It is probably similar on Ubuntu. CentOS/Fedora users will hopefully be able to figure out the equivalent.

Miners: If you currently use Namecoin Core 64-bit with your own patches, and you are unable to build a 32-bit binary on your own, we can try to make a custom Gitian build for you, if you can provide us with the patches you use. If you do not wish your patches to be disclosed publicly, that's fine; contact us to arrange a method of getting them to us privately.

Please report any issues with this build in this thread. Thanks for your patience.
Jeremy Rand, Lead Namecoin Application Engineer
NameID: id/jeremy
DyName: Dynamic DNS update client for .bit domains.

Donations: BTC 1EcUWRa9H6ZuWPkF3BDj6k4k1vCgv41ab8 ; NMC NFqbaS7ReiQ9MBmsowwcDSmp4iDznjmEh5

Luke-Jr
Posts: 13
Joined: Wed Aug 10, 2011 3:33 am
os: linux

Re: Warning: OpenSSL Consensus Bug

Post by Luke-Jr » Sat Aug 01, 2015 5:22 pm

I also gitian built:

1ba336184427b2ab297140967039faea73e352757651f389aef820d3a80abcdf namecoin-0.11.99-linux32.tar.gz

phelix
Posts: 1625
Joined: Thu Aug 18, 2011 6:59 am

Re: Warning: OpenSSL Consensus Bug

Post by phelix » Sun Aug 02, 2015 8:41 am

OP updated
nx.bit - some namecoin stats
nf.bit - shortcut to this forum

mmpool
Posts: 2
Joined: Sun Aug 02, 2015 10:39 pm

Re: Warning: OpenSSL Consensus Bug

Post by mmpool » Sun Aug 02, 2015 10:42 pm

Just letting you know that mmpool is now running namecore.

biolizard89
Posts: 1932
Joined: Tue Jun 05, 2012 6:25 am
os: linux

Re: Warning: OpenSSL Consensus Bug

Post by biolizard89 » Sun Aug 02, 2015 11:38 pm

mmpool wrote:Just letting you know that mmpool is now running namecore.
Thank you for letting us know. Cheers.
Jeremy Rand, Lead Namecoin Application Engineer
NameID: id/jeremy
DyName: Dynamic DNS update client for .bit domains.

Donations: BTC 1EcUWRa9H6ZuWPkF3BDj6k4k1vCgv41ab8 ; NMC NFqbaS7ReiQ9MBmsowwcDSmp4iDznjmEh5

DrHaribo
Posts: 13
Joined: Wed Nov 14, 2012 9:37 pm
Contact:

Re: Warning: OpenSSL Consensus Bug

Post by DrHaribo » Mon Aug 03, 2015 1:44 pm

Bitminter just had 3 blocks orphaned that were made with 64-bit namecoin core.

How far are we from BIP66 going into effect now, making 32-bit unnecessary?
▶▶▶ Bitminter.com - Your trusted mining pool since 2011.

biolizard89
Posts: 1932
Joined: Tue Jun 05, 2012 6:25 am
os: linux

Re: Warning: OpenSSL Consensus Bug

Post by biolizard89 » Mon Aug 03, 2015 2:01 pm

DrHaribo wrote:Bitminter just had 3 blocks orphaned that were made with 64-bit namecoin core.

How far are we from BIP66 going into effect now, making 32-bit unnecessary?
F2Pool told me yesterday that they plan to start enforcing BIP66 when 80% of the past 1000 blocks are version 3 (mined with Namecoin Core). At the time, the current numbers were 78.3% of past 1000, and 90% of last 100. So, I'm guessing it will be very soon. I asked F2Pool to notify me when it took effect; I'll post here when I hear more.

If you're having blocks orphaned, it's possible that maybe F2Pool already started enforcing BIP66, and you built on a block that's version 1. If that's the case, then your problem will end as soon as version 3 blocks reach 95% of past 1000 blocks, which will happen fast since F2Pool will be rejecting all blocks that aren't version 3. What percentage of your blocks are being successfully accepted by the network?
Jeremy Rand, Lead Namecoin Application Engineer
NameID: id/jeremy
DyName: Dynamic DNS update client for .bit domains.

Donations: BTC 1EcUWRa9H6ZuWPkF3BDj6k4k1vCgv41ab8 ; NMC NFqbaS7ReiQ9MBmsowwcDSmp4iDznjmEh5

Post Reply