Bitcoin Forum
April 16, 2014, 11:07:48 PM *
News: ♦♦ A bug in OpenSSL, used by Bitcoin-Qt/Bitcoin Core, could allow your bitcoins to be stolen. Immediately updating Bitcoin Core to 0.9.1 is required in some cases, especially if you're using 0.9.0. Download. More info.
The same bug also affected the forum. Changing your forum password is recommended.
 
  Home Help Search Donate Login Register  
  Show Posts
Pages: 1 2 3 [4] 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 ... 109
61  Bitcoin / Bitcoin Discussion / Re: Bitcoin-Qt / bitcoind version 0.8.4 released, fixes critical DoS vulnerability on: September 08, 2013, 01:55:31 AM
There seems to be a major bug in the Mac version, it keeps showing and error in the database and makes me re-download the blockchain everytime I try to open the client. I had to revert back to the old version to be able to download the blockchain and access my wallet.

Most likely explanation is one of your blockchain data files is corrupted, but the old version doesn't care. You might be serving up a corrupted blocks to anybody who downloads from you, but you wouldn't notice that either.
62  Bitcoin / Development & Technical Discussion / Re: Building headless Bitcoin and Bitcoin-qt on Windows on: September 04, 2013, 04:25:14 AM
I wrote a big comment in init.cpp describing how shutdown works:

Code:
//
// Thread management and startup/shutdown:
//
// The network-processing threads are all part of a thread group
// created by AppInit() or the Qt main() function.
//
// A clean exit happens when StartShutdown() or the SIGTERM
// signal handler sets fRequestShutdown, which triggers
// the DetectShutdownThread(), which interrupts the main thread group.
// DetectShutdownThread() then exits, which causes AppInit() to
// continue (it .joins the shutdown thread).
// Shutdown() is then
// called to clean up database connections, and stop other
// threads that should only be stopped after the main network-processing
// threads have exited.
//
// Note that if running -daemon the parent process returns from AppInit2
// before adding any threads to the threadGroup, so .join_all() returns
// immediately and the parent exits from main().
//
// Shutdown for Qt is very similar, only it uses a QTimer to detect
// fRequestShutdown getting set, and then does the normal Qt
// shutdown thing.
//

I don't know nuthin about Windows' SetConsoleCtrlHandler(), but just setting the fRequestShutdown global variable should do the right thing.
63  Bitcoin / Bitcoin Discussion / Re: Bitcoin-Qt / bitcoind version 0.8.4 released, fixes critical DoS vulnerability on: September 04, 2013, 04:17:31 AM
I just downloaded 2 different SHASUMS.asc within an hour from from sourceforge ... what's going on?

My build environment changed and the first -linux.tar.gz contained ._foo files (see http://superuser.com/questions/61185/why-do-i-get-files-like-foo-in-my-tarball-on-os-x ).

So I untarred and re-tarred with the magic "don't be clever, please, OSX" environment variable set and uploaded a new .tar.gz and SHASUMS.
64  Bitcoin / Bitcoin Discussion / Bitcoin-Qt / bitcoind version 0.8.4 released, fixes critical DoS vulnerability on: September 04, 2013, 01:22:54 AM
Bitcoin-Qt version 0.8.4 is now available from:
  http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.4/

This is a maintenance release to fix a critical bug and three
security issues; we urge all users to upgrade.

Please report bugs using the issue tracker at github:
  https://github.com/bitcoin/bitcoin/issues


How to Upgrade
--------------

If you are running an older version, shut it down. Wait
until it has completely shut down (which might take a few minutes for older
versions), then run the installer (on Windows) or just copy over
/Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).

If you are upgrading from version 0.7.2 or earlier, the first time you
run 0.8.4 your blockchain files will be re-indexed, which will take
anywhere from 30 minutes to several hours, depending on the speed of
your machine.

0.8.4 Release notes
===================

Security issues
---------------

An attacker could send a series of messages that resulted in
an integer division-by-zero error in the Bloom Filter handling
code, causing the Bitcoin-Qt or bitcoind process to crash.
Bloom filters were introduced with version 0.8, so versions 0.8.0
through 0.8.3 are vulnerable to this critical denial-of-service attack.

A constant-time algorithm is now used to check RPC password
guess attempts; fixes https://github.com/bitcoin/bitcoin/issues/2838
(CVE-2013-4165)

Implement a better fix for the fill-memory-with-orphan-transactions
attack that was fixed in 0.8.3. See
https://bitslog.wordpress.com/2013/07/18/buggy-cve-2013-4627-patch-open-new-vectors-of-attack/
for a description of the weaknesses of the previous fix.
(CVE-2013-4627)

Bugs fixed
----------

Fix multi-block reorg transaction resurrection.

Fix non-standard disconnected transactions causing mempool orphans.
This bug could cause nodes running with the -debug flag to crash.

OSX: use 'FD_FULLSYNC' with LevelDB, which will (hopefully!)
prevent the database corruption issues many people have
experienced on OSX.

Linux: clicking on bitcoin: links was broken if you were using
a Gnome-based desktop.

Fix a hang-at-shutdown bug that only affects users that compile
their own version of Bitcoin against Boost versions 1.50-1.52.

Other changes
-------------

Checkpoint at block 250,000 to speed up initial block downloads
and make the progress indicator when downloading more accurate.


Thanks to everybody who contributed to the 0.8.4 releases!
----------------------------------------------------------

Pieter Wuille
Warren Togami
Patrick Strateman
pakt
Gregory Maxwell
Sergio Demian Lerner
grayleonard
Cory Fields
Matt Corallo
Gavin Andresen
65  Bitcoin / Project Development / Re: Is Mastercoin bloating the blockchain and what we can do about it? on: August 30, 2013, 07:29:22 AM
It bloats the UTXO set, which is bad.

MasterCoin transactions should all be spendable or provably prune-able. There are plenty of ways to accomplish that, the easiest of which that works today would be to stuff data into unused public keys of an OP_CHECKMULTISIG transaction.
66  Bitcoin / Project Development / Re: Giveaway Thread for "MasterCoins" - the new protocol layer built on bitcoin on: August 30, 2013, 07:26:44 AM
Please stop!

Yes, please stop polluting the UTXO set. There are much better ways to accomplish what you want to accomplish.
67  Bitcoin / Development & Technical Discussion / Re: [ANN] EasyWinBuilder - The Easy Way to Build Bitcoin on Windows on: July 31, 2013, 12:04:05 AM
So, one thought:

Instead of "staging" all of the dependencies and then modifying the makefile/.pro to look for the dependencies in six different places, it would be cleaner to configure with --prefix=<somewhere>  and then 'make install' to put all the dependency libraries/include files in one spot. Ideally, none of the makefiles/.pro files would contain specific version numbers for anything.

Specific notes as I worked through doing that on a Windows system, putting dependencies in C:\deps :

Openssl:  /bin/perl Configure --prefix=/c/deps mingw ...etc

BDB: ../dist/configure --prefix=/c/deps ...etc

Boost: b2.exe --layout=system --prefix=C:\deps link=static threading=multi runtime-link=static toolset=gcc ...etc

Qt: configure.exe -prefix=C:\deps -I "C:\deps\include" -L "C:\deps\lib" ...etc

68  Bitcoin / Development & Technical Discussion / Re: Help with Bitcoin JSON RPC - more SLOOOWness on: July 29, 2013, 12:24:01 AM
How big is your wallet?

getbalance() is O(N) where N is the total number of transactions in the wallet. (actually, it can be even worse than O(N) if you have long chains of unconfirmed transactions in your wallet)

"Patches welcome" to fix that, I expected one of the big bitcoind-using services would submit a performance fix patch long ago.

69  Bitcoin / Development & Technical Discussion / Re: How to miners decide which transactions to include in a block? on: July 29, 2013, 12:16:49 AM
so, for a solo miner using bitcoin-qt, that decide what goes into a block? is it configurable? Huh
It's not. You need to modify the client from the source.

That's incorrect. The following command-line or bitcoin.conf configuration parameters let miners set their transaction acceptance policy:

Quote
-blockminsize=<n>      Set minimum block size in bytes (default: 0)
 -blockmaxsize=<n>      Set maximum block size in bytes (default: 250000)
 -blockprioritysize=<n> Set maximum size of high-priority/low-fee transactions in bytes (default: 27000)
 

The -mintxfee / -minrelaytxfee options currently control how large a fee-per-kilobyte is needed for a transaction to be considered "fee paying" versus "free".
70  Bitcoin / Bitcoin Discussion / Re: Bitcoin-Qt next-test 2013-07-21 on: July 23, 2013, 10:59:22 PM
I set the topic as sticky for a while because I think that if anything needs extensive testing it's the software that handles our money.

I would much rather people help test individual pull requests or 'git HEAD' rather than "random collection of changes". Putting eleven unrelated changes together makes figuring out what caused a bug/regression much harder.
71  Bitcoin / Development & Technical Discussion / Re: Building headless Bitcoin and Bitcoin-qt on Windows on: July 20, 2013, 06:17:11 AM
I spent a bunch of time getting the mingw-cross-compiled Qt compiled with -openssl-linked for the payment protocol work (it uses QtNetwork to fetch PaymentRequest/PaymentACK messages via https).

The magic configure incantation was:
Quote
  # Compile static libraries, and use statically linked openssl (-openssl-linked):
  OPENSSL_LIBS="-L$DEPSDIR/openssl-1.0.1c -lssl -lcrypto -lgdi32" ./configure -prefix $INSTDIR -I $DEPSDIR/openssl-1.0.1c/include  -confirm-license -release -opensource -static -no-qt3support -xplatform unsupported/win32-g++-cross -no-multimedia -no-audio-backend -no-phonon -no-phonon-backend -no-declarative -no-script -no-scripttools -no-javascript-jit -no-webkit -no-svg -no-xmlpatterns -no-sql-sqlite -no-nis -no-cups -no-iconv -no-dbus -no-gif -no-libtiff -no-opengl -nomake examples -nomake demos -nomake docs -no-feature-style-plastique -no-feature-style-cleanlooks -no-feature-style-motif -no-feature-style-cde -no-feature-style-windowsce -no-feature-style-windowsmobile -no-feature-style-s60 -openssl-linked

Nothing special needed to be done for the openssl build:

Quote
./Configure --cross-compile-prefix=i586-mingw32msvc- mingw


The payment protocol code add a couple more depedencies to Bitcoin-Qt:

+ QtNetwork with OpenSSL support
+ Google's protocol buffer library and compiler.

72  Bitcoin / Development & Technical Discussion / Re: [ANN] EasyWinBuilder - The Easy Way to Build Bitcoin on Windows on: July 10, 2013, 06:14:47 AM
Nice work!

RE: gcc creating different binaries:

The gitian build does two main things to make builds reproducible:

1. Uses libfaketime.so so all calls to time()/etc during compilation return the same time.
 (I don't know if it is the compiler, linker, or archiver that likes to put timestamps in binaries)

2. Passes -frandom-seed=constant  to g++, so it doesn't create random names for generated methods.

73  Bitcoin / Development & Technical Discussion / Re: The network is flooded with spam on: July 08, 2013, 08:09:31 PM
The problem is that there is a mismatch between the criteria used to accept a transaction into the memory pool / relayed and the criteria most miners use to choose transactions for their blocks.

The fix is not conceptually hard; just modify the memory pool code so the memory pool is treated like it is an extra-large block, and only relay/store the transactions that are likely to be mined in the next few blocks.

That hasn't been implemented yet because it just hasn't been a high priority.
74  Bitcoin / Bitcoin Discussion / Bitcoin-Qt / bitcoind version 0.8.3 released on: June 25, 2013, 05:59:17 PM
Bitcoin-Qt version 0.8.3 is now available from:
  http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.3/

This is a maintenance release to fix a denial-of-service attack that
can cause nodes to crash.

Please report bugs using the issue tracker at github:
  https://github.com/bitcoin/bitcoin/issues

0.8.3 Release notes

Truncate over-size messages to prevent a memory exhaustion attack.

Fix a regression that causes excessive re-writing of the 'peers.dat' file.



Thanks to Peter Todd for responsibly disclosing the vulnerability
( CVE-2013-4627 ) and creating a fix.
75  Bitcoin / Development & Technical Discussion / Re: Manually editing the wallet.dat file on: June 09, 2013, 04:38:03 PM
No.
76  Economy / Computer hardware / Re: WTS: BFL 5 GH/s ASIC miner on: June 09, 2013, 04:36:44 PM
Sold!  (I hope)

Two offers over 26 BTC, best offer was 30 BTC.
77  Bitcoin / Development & Technical Discussion / Re: What if the devs are ordered by a US judge to include a government backdoor? on: June 06, 2013, 05:16:03 PM
Let's say the IRS wants to be able to confiscate bitcoins from tax evaders. So they go to the US courts to get this. A judge ends up ordering the bitcoin.org dev team to include a government backdoor so the IRS can take funds away from those who don't pay taxes.

The devs would be forced to comply right?

Pieter and Wladimir are not US citizens, so a US judge can't order them to do anything.

If I was ordered to insert a backdoor, I'd just resign as lead developer and find something else to work on.

But this whole scenario sounds like a paranoid delusion; has there EVER been a case where a judge has ordered a software developer to do anything other than stop distributing their software (because of some copyright or patent issue) ?
78  Economy / Computer hardware / Re: WTS: BFL 5 GH/s ASIC miner on: June 06, 2013, 05:00:37 PM
Will it make 26BTC over the useful life of this device?
It is mining over 0.2 BTC per day right now, so if difficulty doesn't change (HAH!) and you have free electricity (DOUBLE HAH!) you'll break even in 4 or 5 months.

PS: best offer so far is a private offer of 26 BTC plus shipping.
79  Bitcoin / Bitcoin Discussion / Re: Ruh Roh, bitcoin on the radar of the IMF? on: June 05, 2013, 05:05:43 PM
Thoughts?

This gives me warm fuzzies; a University of Chicago professor speculating about how a wildly successful Bitcoin might affect the International Monetary Fund!

I don't really care what is said, just the fact that Bitcoin is being talked about in the elite Ivory Towers is a very good thing.

80  Bitcoin / Development & Technical Discussion / Re: Please do not change MAX_BLOCK_SIZE on: June 04, 2013, 05:59:30 PM
Every point presented on this subject has already being addressed. Multiple times.

Yes.  If you're feeling helpful, please create a wiki page or other document that organizes all of the pro/con arguments: economic and technical. And maybe another wiki page that organizes all of the various proposals for how to increase the block size.

I've been derailed the last week by a death in the family, and still need to finish up some payment protocol work.
Pages: 1 2 3 [4] 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 ... 109
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!