Topic: Help test: version 0.6.3 release candidate 1 - page 2. (Read 25671 times)

Most people are stupid, and they might not realize what that command does.

No I had problems before upgrading, you should check gmail.

Is their any way I can 'rm -r .bitcoin' and still have access to all of my coins? Yes, of course their is. 1. Back-up wallet.dat 2. Make a paper back-up 3. Import the keys from another existing offline wallet.

I try to gauge each vulnerability in an objective way for the classifications on the Bitcoin CVE list.

well I am sorry you see it that way gmaxwell
let me look back over the (public) logs from that chanel

https://bitcointalk.org/index.php?topic=88734.20

some other conversation
Graet: "Meh" on that. It's getting called a serious vulnerability in part because of the preferences of the person who reported it. I wouldn't have called it that on my own, and it's of a class of DOS attacks that have been discussed in public before.
some other stuff not related
well gmaxwell we need some (oh god again) standards - so ppls opinions have some meaning
if a dev announcves a serious vuln - it shouldnt be a "matter of opinion"

"highly offensive" and "entitled" ?
Public channel logs: bit.ly/iPFi3X

Some people talk about getting standards in place - some don't seem to care so much, for over a year I have been idling in -dev and seen the "standards" topic come up over and again
if I have caused offence by asking for a standard I apologise. Maybe I shouldn't have "(oh god again)" but from an observers point....the topic comes up often.

I may not have said "thank you for improving bitcoin" in as many words, but many times i have told the devs "good work" with a smile or other meaning the same thing, and have said thanks when someone has helped me directly.

If we had some consensus from the devs already as to what is "severe" and a "critical" and a "trivial" rather than them choosing to announce levels based on individual opinion this discussion would never have occurred.

Thank you for the RC I look forward to the release version.

proxy is not working

my log continues to show:

06/21/2012 03:16:19 ERROR: Proxy error: general failure

This is under both SOCKS4 and SOCKS5

Doing this will delete your wallet.  Please edit your post to include some kind of warning so that if anyone else hits this they don't just blindly follow your instructions and lose coin.

My best guess on your issue is that you didn't shutdown cleanly before upgrading. Deleting your databases is one way to recover from that, but users with coin should take care to not delete their wallets in the process.

DO NOT DO THIS IF YOU HAVE BITCOINS, IT WILL DESTROY THEM IRRECOVERABLY

Say "thank you for improving bitcoin"?   On IRC you seriously offended me with what I considered to be an entitled attitude and unjustified hostility.  I was particularly torqued after I said that I didn't agree that it was "critical" and wouldn't have personally described it that way and based on that you continued to repeat allegations that there were no standards and that the developers don't agree about vulnerabilities. I think I would know if I didn't agree with what Gavin posted.

I apologize if my willingness to argue back managed to keep us from effectively communicating. For all the trouble you'll have with your nodes keep in mind that we all work hard with Bitcoin too. I maintain more nodes than you do— though I do have the comfort of not handling a large flow of other people's money, I am  constantly dealing with juggling changes on them.

The issue at question is a (set of) DOS attacks, as described in the announcement.  They've been 'disclosed' for a month in git, and have been discussed in the abstract by class as long as a year ago.  We have not historically done embargoed releases and early warnings to major infrastructure on issues which didn't allow the theft of Bitcoin or ~O(1) knockout of the network, and I would stridently oppose beginning such a practice: We do not have the resources to manage that, and it would delay getting fixes into the hands of users.  This release announcement is not the first public mention of these issues, and standard best practices for node operation will generally protect you from DOS attacks.

You should handle this like you'd handle other testing releases: Upgrade one or two of your nodes and report issues. If you do not run testing version the release versions will likely not be of any higher quality. If by some crazy chance someone DOS attacks your other nodes, you at least have some that are working.

I experienced a problem with 0.6.2, DB_error. When I noticed this thread I tried it and still received the message below:


I did an:
Mod edit: NEVER EVER DO THAT. YOU WILL PERMANENTLY DELETE YOUR BITCOINS!

Not a Fool edit: Why ADD Crud To My Post, Is this Really Necessary? All my coins are paper backups.

Everything is now downloading fine. In hindsight, I probably could've just zipped everything up and set it aside or pass it along to someone that couldv'e poked at it to see why.

The vulnerability itself is not disclosed still. I've finished tagging stable in git, the formal release is just waiting on binaries.

Um releasing a testing version and announcing a potential vulnerability in the same thread??
I think you did better here
https://bitcointalksearch.org/topic/ann-critical-vulnerability-denial-of-service-attack-81749

as a pool operator I now feel in a bind, I must update to a RC (that you have asked ppl to test) because you announced a vulnerability
So I risk updating 6 or 7 nodes to find the test crashes or I wait for stable and hope no-one uses the vuln against my pool in meantime.

what can I say....

Thanks for the info Gavin,

I followed these steps and now 0.6.3 is running fine on 64-bit Xubuntu 11.04.

Note 1: While waiting the 10 minutes or so to shutdown using the -detachdb option the GUI looks like it's not responding.
Note 2: Before I copied the blk* files, I needed ~1350 blocks to synchronize with the network but when I restarted 0.6.3 the count was only ~1050 blocks. After a couple of minutes, the count increased to ~1225.
Note 3: I was only able to connect to 8 nodes on 0.6.3 even though the bitcoin.conf hasn't changed and I normally connect to +100 nodes.

Seems to work fine here on slackware-current 64bit as well as kubuntu 12.04 64bit.
But it would be nice if gpg signatures could be included the next time 

works on win7 64-bit.

Before you copy the blk* files, you must run with the -detachdb option and make sure you shutdown bitcoin and wait for it to exit completely.  With 0.6.2, we change the default from "take a long time to shut down, but leave standalone .dat files" to "shutdown quickly, but leave .dat files that are tied to the database/log.* files".

Too many ordinary users were quitting bitcoin and then immediately powering off their systems, leaving the database in a bad state.

It was running fine when I first launced 0.6.3 and began downloading the blockchain from scratch.

I then quit before the entire block chain downloaded and moved a copy of these 3 files from 0.6.2 residing on another computer:

bitcoin.conf
blk0001.dat
blkindex.dat

Once I tried to relauch bitcoin-qt, I get this error:


OS: Xubuntu 11.04

A very helpful member helped me out...


Thank you... Works fine now

Loaded and synchronizing blockchain fine on Mac OS X 10.6.8 64-bit.
(I haven't tried sending or receiving coins as I have none on this computer.)

It's readable if you zoom in. http://img607.imageshack.us/img607/2962/bitcoinerror.jpg

I transcribed it for you: