Search content
Sort by
Showing 20 of 2,578 results by error
I bought this domain intending to set up a blockchain project, and several other people made much better ones than I could have.
You could use it for your own blockchain app, news archives, or several other possibilities.
Not really sure how much this is worth, so I'm looking for reasonable offers. BTC preferred.
You could use it for your own blockchain app, news archives, or several other possibilities.
Not really sure how much this is worth, so I'm looking for reasonable offers. BTC preferred.
Re: Bitcoin RPM packages for Fedora and Red Hat Enterprise Linux
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.
Re: Bitcoin RPM packages for Fedora and Red Hat Enterprise Linux
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.
Re: Bitcoin RPM packages for Fedora and Red Hat Enterprise Linux
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.
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.
Re: Bitcoin RPM packages for Fedora and Red Hat Enterprise Linux
~/.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?
Re: Bitcoin RPM packages for Fedora and Red Hat Enterprise Linux
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.
Re: Bitcoin RPM packages for Fedora and Red Hat Enterprise Linux
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.
Re: Bitcoin RPM packages for Fedora and Red Hat Enterprise Linux
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.
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.
Re: Bitcoin RPM packages for Fedora and Red Hat Enterprise Linux
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.
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.
Re: Bitcoin RPM packages for Fedora and Red Hat Enterprise Linux
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.
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.
Anyone else just go out and do a dry run of their DB backup?
Backups are all well and good, but you need to remember to test restores!
Here it is - https://bitcointalk.org/index.php?topic=449010.msg8400897#msg8400897
Site is http://adbit.co/
Site is http://adbit.co/
Thanks. I would have never found that myself
Oh man, they have a right to be panicking.
Strange that they say it happened last night but no ones been mentioning it here.
Strange that they say it happened last night but no ones been mentioning it here.
I don't think it's a very large website or I would have seen it here or on reddit, and I didn't. But I figure if anyone does know what it was, it would be here.
How did you find this?
I've been on Stack Overflow for years...
For the love of gawd...
http://serverfault.com/q/622020/126632
Note to developers: The fact that you can install Ubuntu successfully and use things like Docker, Heroku and AWS does not make you competent at operations.
Please, please, if you're going to start anything that involves Bitcoin, or other people's money in general, be sure you have a competent system administrator looking after things and making sure there are no business-killing mistakes in the environment, like lack of working backups, using Ubuntu as a server, systems not being properly secured, etc.
P.S. I'd love to know which website this was, as I didn't see any news about a well-known site being down after a brief look in the usual places.
http://serverfault.com/q/622020/126632
Quote
The website is fairly large, deals with Bitcoin, there's thousands of dollars in account balances possibly lost, and I'm panicking. ... I do not have a recent backup.
Note to developers: The fact that you can install Ubuntu successfully and use things like Docker, Heroku and AWS does not make you competent at operations.
Please, please, if you're going to start anything that involves Bitcoin, or other people's money in general, be sure you have a competent system administrator looking after things and making sure there are no business-killing mistakes in the environment, like lack of working backups, using Ubuntu as a server, systems not being properly secured, etc.
P.S. I'd love to know which website this was, as I didn't see any news about a well-known site being down after a brief look in the usual places.
Re: Bitcoin RPM packages for Fedora and Red Hat Enterprise Linux
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.
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.
Re: Bitcoin RPM packages for Fedora and Red Hat Enterprise Linux
Sounds like a struggle. It is a little surprising to find such disharmony between the development projects and all the distros in the Linux world, although I'm beginning to understand just how many levels of interoperation there are (packaging format, desktop, architecture, repo & EOL distros/libraries all play their part, I'll hazard a guess that there are more...). Seems like the secret is to have as consumate a knowledge of Linux in all it's incarnations and permutations as possible, then it's possible to fix most things yourself 
.
.It's not that. The Bitcoin devs aren't hard to work with. The problem is Bitcoin wasn't originally designed with distro packaging in mind, and almost nobody (except possibly me) cares about it. I just want to see Bitcoin used more widely and more securely. Eventually getting Bitcoin into Fedora and Red Hat will help a LOT. And having used Linux for 20 years I have a little experience to draw on.
Unfortunately I don't get paid for this and the donations have been pitifully small so far. Oh well. I'll keep at it.Re: Bitcoin RPM packages for Fedora and Red Hat Enterprise Linux
Working now. yum has found bitcoin.x86_64 0:0.9.2.1-1.fc20 again, and the Qt wallet is working as it was. Thanks error!
The situation with using bitcoind/bitcoin-server as a service is still difficult with Qubes. I believe what's happening is mirroring what happens also with bitcoin-qt when it's configured to use /var/lib/bitcoin as the datadir, namely that the blocks download but aren't/cannot be written to disk (if I quit and restart bitcoin-qt when it's reportedly dl-ing the blockchain to /var/lib/bitcoin, the block count starts from 0). If I run systemctl start bitcoin, Armory detects that bitcoind is running, but it doesn't see any new blocks, so it appears that bitcoind is behaving the same way bitcoin-qt does, despite having permission to access /var/lib/bitcoin. I'm thinking that this is because Qubes has SELinux set disabled by default (yum install bitcoin-server yields a page of permissions warnings).
It'd be incredibly cool to get bitcoind/bitcoin-server working as a service on Qubes-OS, using Armory would appear much less cluttered. However, I've figured out how to establish a Bitcoin-Qt desktop item that runs in Node mode (-disablewallet argument), so it's not so bad this way. Does Qubes need it's own dedicated package to install and configure bitcoind? I'm thinking that's possibly the case.
The situation with using bitcoind/bitcoin-server as a service is still difficult with Qubes. I believe what's happening is mirroring what happens also with bitcoin-qt when it's configured to use /var/lib/bitcoin as the datadir, namely that the blocks download but aren't/cannot be written to disk (if I quit and restart bitcoin-qt when it's reportedly dl-ing the blockchain to /var/lib/bitcoin, the block count starts from 0). If I run systemctl start bitcoin, Armory detects that bitcoind is running, but it doesn't see any new blocks, so it appears that bitcoind is behaving the same way bitcoin-qt does, despite having permission to access /var/lib/bitcoin. I'm thinking that this is because Qubes has SELinux set disabled by default (yum install bitcoin-server yields a page of permissions warnings).
It'd be incredibly cool to get bitcoind/bitcoin-server working as a service on Qubes-OS, using Armory would appear much less cluttered. However, I've figured out how to establish a Bitcoin-Qt desktop item that runs in Node mode (-disablewallet argument), so it's not so bad this way. Does Qubes need it's own dedicated package to install and configure bitcoind? I'm thinking that's possibly the case.
I'm not sure what the deal with Qubes OS is. When I get some time I'll play with it and see if I can figure out what's going on. I can't make any guarantees, though; it seems they have a completely different security model and who knows what it will need to run the bitcoin server successfully.
Right now, though, the more important thing is doing something about this horrible configuration file handling code. It's old, old code from Bitcoin that isn't at all object oriented and is very brittle. It got even more brittle with the 0.9 refactoring, which is where this latest issue came from. I _finally_ think I have a workaround, but I'm going to give it a few rounds of testing locally before I push it out. Eventually all this code really needs to be scrapped and rewritten.
Re: Bitcoin RPM packages for Fedora and Red Hat Enterprise Linux
Edit: just tried since your rebuild, same error
You sure you ran
Code:
yum clean all
? The repos look fine now.