|
error (OP)
|
 |
January 08, 2015, 09:48:56 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... 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. |
3KzNGwzRZ6SimWuFAgh4TnXzHpruHMZmV8
|
|
|
|
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
marcus_of_augustus
Legendary
 Offline
Activity: 3920
Merit: 2348
Eadem mutata resurgo
|
|
January 08, 2015, 09:53:12 PM |
|
do you have any update what the progress is on getting secp256k1 openssl support in the repos?
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 (OP)
|
|
January 08, 2015, 09:58:09 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. |
3KzNGwzRZ6SimWuFAgh4TnXzHpruHMZmV8
|
|
|
|
error (OP)
|
|
January 11, 2015, 12:20:36 AM |
|
~/.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?>>>  ?? You copied and pasted someone else's post from months ago. Do you have something of your own to say? |
3KzNGwzRZ6SimWuFAgh4TnXzHpruHMZmV8
|
|
|
|
error (OP)
|
|
January 11, 2015, 07:41:27 AM |
|
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. |
3KzNGwzRZ6SimWuFAgh4TnXzHpruHMZmV8
|
|
|
|
|
|
error (OP)
|
|
February 27, 2015, 07:43:14 PM |
|
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. |
3KzNGwzRZ6SimWuFAgh4TnXzHpruHMZmV8
|
|
|
backslash
Newbie
Offline
Activity: 7
Merit: 0
|
|
February 27, 2015, 07:52:33 PM |
|
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 (OP)
|
|
February 27, 2015, 08:00:20 PM |
|
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. |
3KzNGwzRZ6SimWuFAgh4TnXzHpruHMZmV8
|
|
|
backslash
Newbie
Offline
Activity: 7
Merit: 0
|
|
February 27, 2015, 08:18:25 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 |
|
|
|
|
chrysophylax
Legendary
Offline
Activity: 2814
Merit: 1091
--- ChainWorks Industries ---
|
|
September 05, 2015, 01:44:08 PM |
|
i know im posting to an old thread - but bloody amazing to see ...
what are the latest developments? ...
#crysx
|
|
|
|
marcus_of_augustus
Legendary
Offline
Activity: 3920
Merit: 2348
Eadem mutata resurgo
|
|
September 05, 2015, 10:13:22 PM |
|
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
Offline
Activity: 2814
Merit: 1091
--- ChainWorks Industries ---
|
|
September 06, 2015, 01:55:52 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 |
|
|
|
|
