Bitcoin RPM packages for Fedora and Red Hat Enterprise Linux

chrysophylax

legendary

Activity: 2912

Merit: 1091

--- ChainWorks Industries ---

Quote from: marcus_of_augustus on September 05, 2015, 05:13:22 PM

Quote from: chrysophylax on September 05, 2015, 08:44:08 AM

i know im posting to an old thread - but bloody amazing to see ...

what are the latest developments? ...

#crysx

Recently secp256k1 EC curve was included in RH openssl repo packages. Last I saw it was in the "Testing" repo.

nice ...

so this may be finally that redhat decide to be up to date like everyone else? ... or are they still running around like scared little cats on a stormy night? ...

im a redhat guy also - and i gave up watching the rubbish that redhat legal were doing ...

it stagnated the uptake of the OS and stagnated the advancment of people like myself who use nothing but redhat OS systems ... in all the servers and all the workstations and all the miners ...

we can only hope ...

so this means that this repo development will be shut down? ...

i quite like it - and error was doing a great job ...

id like to see this repo continue - and add more to it - not just updates ... id be happy to have our coin as part of it - and definitely not without reimbursment ...

ideas ideas ideas ...

#crysx

marcus_of_augustus

legendary

Activity: 3920

Merit: 2349

Eadem mutata resurgo

Quote from: chrysophylax on September 05, 2015, 08:44:08 AM

i know im posting to an old thread - but bloody amazing to see ...

what are the latest developments? ...

#crysx

Recently secp256k1 EC curve was included in RH openssl repo packages. Last I saw it was in the "Testing" repo.

chrysophylax

legendary

Activity: 2912

Merit: 1091

--- ChainWorks Industries ---

i know im posting to an old thread - but bloody amazing to see ...

what are the latest developments? ...

#crysx

backslash

newbie

Activity: 7

Merit: 0

Quote from: error on February 27, 2015, 03:00:20 PM

But secp256k1 still needs a blessing from Red Hat Legal. See BZ#1021898.

This will not happen soon. RH was given the permission from the NSA to use the NIST curves. Most of the EC curves have patents (Certicom) on their speedup implementation. The NSA acquired the rights for the NIST curves from Certicom, if I am not mistaken. So RH will only ever provide the NIST curves, until the legal situation is clear.

See http://en.wikipedia.org/wiki/ECC_patents

error

hero member

Activity: 588

Merit: 500

Quote from: backslash on February 27, 2015, 02:52:33 PM

Quote from: error on February 27, 2015, 02:43:14 PM

Quote from: backslash on February 27, 2015, 02:07:04 PM

check this out: http://harald.hoyer.xyz/files/bitcoin-0.10.0-1.fc21.src.rpm .. bitcoind without openssl-compat on F21 .. only with libsecp256k1

Someone built 0.10.0 with a highly bastardized version of my 0.8.5 specfile? And also disabled a bunch of stuff, like bitcoin-qt, libbitcoinconsensus, the command line utilities...

I'll have a play later with whatever this process actually builds, and see if it can be better integrated. But the real holdup isn't libsecp256k1, it's Red Hat Legal.

Yeah, sorry.. I just wanted the server without any openssl modifications.

That's fine, I want to get rid of openssl too. When I tried a test build (a few weeks ago against an RC) it failed, so I kept it. But secp256k1 still needs a blessing from Red Hat Legal. See BZ#1021898.

backslash

newbie

Activity: 7

Merit: 0

Quote from: error on February 27, 2015, 02:43:14 PM

Quote from: backslash on February 27, 2015, 02:07:04 PM

check this out: http://harald.hoyer.xyz/files/bitcoin-0.10.0-1.fc21.src.rpm .. bitcoind without openssl-compat on F21 .. only with libsecp256k1

Someone built 0.10.0 with a highly bastardized version of my 0.8.5 specfile? And also disabled a bunch of stuff, like bitcoin-qt, libbitcoinconsensus, the command line utilities...

I'll have a play later with whatever this process actually builds, and see if it can be better integrated. But the real holdup isn't libsecp256k1, it's Red Hat Legal.

Yeah, sorry.. I just wanted the server without any openssl modifications.

error

hero member

Activity: 588

Merit: 500

Quote from: backslash on February 27, 2015, 02:07:04 PM

check this out: http://harald.hoyer.xyz/files/bitcoin-0.10.0-1.fc21.src.rpm .. bitcoind without openssl-compat on F21 .. only with libsecp256k1

Someone built 0.10.0 with a highly bastardized version of my 0.8.5 specfile? And also disabled a bunch of stuff, like bitcoin-qt, libbitcoinconsensus, the command line utilities...

I'll have a play later with whatever this process actually builds, and see if it can be better integrated. But the real holdup isn't libsecp256k1, it's Red Hat Legal.

backslash

newbie

Activity: 7

Merit: 0

check this out: http://harald.hoyer.xyz/files/bitcoin-0.10.0-1.fc21.src.rpm .. bitcoind without openssl-compat on F21 .. only with libsecp256k1

error

hero member

Activity: 588

Merit: 500

A new build of Bitcoin 0.9.3 has been pushed to the repositories.

This build addresses an issue discovered Saturday where Bitcoin nodes using the security fixes in OpenSSL 1.0.1k were not correctly validating blocks.

I have backported a fix for this issue and it is now available for download.

Affected users may have a corrupt database index; if this is the case then the message "Chain state database corruption likely" will appear in the debug.log, and the GUI will state no block source available even with multiple peers connected. Run bitcoind or bitcoin-qt with the -reindex command line option to fix your block chain index. (Warning: This may take several hours, or even longer on slower computers.)

---

Beginning with 0.10.0 (coming soon), RPM package builds run the Bitcoin test suite as part of the build process. This wasn't possible before due to issues with the test suite itself which have since been resolved. Test packages of 0.10.0 rc1 are now in the bitcoin-test repository. Please read the upstream release notes and make a backup of your data directory before installing or upgrading to 0.10.0.

error

hero member

Activity: 588

Merit: 500

Quote from: ?? on ??

~/.config/Bitcoin-Qt.config has the line strDataDir=/home/user/.bitcoin, so my guess is that there's another Bitcoin-Qt.config in either /var/lib/bitcoin or /etc/bitcoin taking precendence. Or something else?>>> Huh

??

You copied and pasted someone else's post from months ago. Do you have something of your own to say?

error

hero member

Activity: 588

Merit: 500

Quote from: marcus_of_augustus on January 08, 2015, 04:53:12 PM

ok, I could help with packaging that if you like. PM me if so.

My intention is to eventually get Bitcoin officially packaged in Fedora and EPEL once these issues are resolved. Currently the ticket for this is bug 1020292 which you can follow.

marcus_of_augustus

legendary

Activity: 3920

Merit: 2349

Eadem mutata resurgo

Quote from: error on January 08, 2015, 04:48:56 PM

Quote from: marcus_of_augustus on January 08, 2015, 04:33:49 PM

do you have any update what the progress is on getting secp256k1 openssl support in the repos?

Quote from: marcus_of_augustus on January 08, 2015, 04:33:49 PM

anyway bitcoin has it's own secp256k1 library on git now so there are other options

I'm going to be taking another look at Bitcoin's libraries with 0.10 and see what the best way to go is.

ok, I could help with packaging that if you like. PM me if so.

error

hero member

Activity: 588

Merit: 500

Quote from: marcus_of_augustus on January 08, 2015, 04:33:49 PM

do you have any update what the progress is on getting secp256k1 openssl support in the repos?

Still blocked by Red Hat's legal department. They're afraid of ghosts under the bed, I guess. Though they did approve secp521r1 some time ago, so I guess maybe they're just really slow...

Quote from: marcus_of_augustus on January 08, 2015, 04:33:49 PM

anyway bitcoin has it's own secp256k1 library on git now so there are other options

I'm going to be taking another look at Bitcoin's libraries with 0.10 and see what the best way to go is.

marcus_of_augustus

legendary

Activity: 3920

Merit: 2349

Eadem mutata resurgo

I stopped following the ridiculous charade that was the 'debate' for keeping ECC out of RH OpenSSL but have noticed that secp256k1 headers are there in the openssl-devel package and ECC functionality/support is generally in the openssl package now ...

do you have any update what the progress is on getting secp256k1 openssl support in the repos?

i.e. what's the latest farcical excuse?

anyway bitcoin has it's own secp256k1 library on git now so there are other options

error

hero member

Activity: 588

Merit: 500

A security update for OpenSSL has been made available today which addresses several security vulnerabilities.

One of these (CVE-2014-3570) impacts 64-bit (x86_64) builds of Bitcoin, at least in theory. The remainder are low and moderate impact security issues, some of which may impact you depending on your configuration (e.g. if you use Bitcoin RPC with SSL/TLS).

Updates for the openssl packages in these repos are now available for x86_64 and i386. ARM builds will be posted in about four hours from now.

Remember to restart Bitcoin after installing the updates.

error

hero member

Activity: 588

Merit: 500

It appears that people in some parts of the United States are having trouble accessing the website and yum repositories.

The server is, of course, up and running fine. The trouble appears to be out on the network somewhere, and while I'm working to track it down, since the problem is not at my end there may be little that I can do.

Sometime in the next few days I'm going to set up rsync and open the repo up for mirroring. Donations toward - or of - a mirror would be appreciated.

---

Edit: Things seem to be fine now, but I'd appreciate reports from anyone who might still be having trouble reaching the repositories.

error

hero member

Activity: 588

Merit: 500

A security update for OpenSSL has been published which resolves four security issues, some of which may impact Bitcoin.

The updated OpenSSL version 1.0.1j is now available for EL and Fedora on x86_64, i386 and ARM (Fedora only) architectures.

Please update your system and then restart your Bitcoin client or server to ensure that you are running the updated code.

infertux

newbie

Activity: 1

Merit: 0

Great work on the RPM packages error, it's nice to have proper SELinux support for Bitcoin.

I made a Chef cookbook which uses your packages - hope that's okay.

error

hero member

Activity: 588

Merit: 500

A security update for OpenSSL has been published which resolves several security issues, some of which may impact Bitcoin.

Please update your system as soon as possible, and then restart your Bitcoin client or server to ensure that you are running the updated code.

Updates are available now for EL and Fedora on x86_64 and i386. Fedora ARM builds will be made available within the next 24 hours.

error

hero member

Activity: 588

Merit: 500

Whoever just bought me a pizza, thanks

Topic: Bitcoin RPM packages for Fedora and Red Hat Enterprise Linux (Read 31450 times)