This is not made possible with Coinbaser. All coinbaser does is allow modifying the content of your coinbase. Nothing else with the usual mining stuff is changed.

Been there, tried that, it blew up...

yes

It's not automatic opt-in. You have to register to get Namecoins.

rc7 was just renamed to final 0.4.1 since no more bugs were found. I guess Gavin forgot to rename the folder... :/

Bitcoin version 0.4.1 is now available for download at:
  http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.4.1/

This is a bugfix only release based on 0.4.0.

Please report bugs by replying to this forum thread.

MAJOR BUG FIX  (CVE-2011-4447)

The wallet encryption feature introduced in Bitcoin version 0.4.0 did not sufficiently secure the private keys. An attacker who
managed to get a copy of your encrypted wallet.dat file might be able to recover some or all of the unencrypted keys and steal the
associated coins.

If you have a previously encrypted wallet.dat, the first time you run wxbitcoin or bitcoind the wallet will be rewritten, Bitcoin will
shut down, and you will be prompted to restart it to run with the new, properly encrypted file.

If you had a previously encrypted wallet.dat that might have been copied or stolen (for example, you backed it up to a public
location) you should send all of your bitcoins to yourself using a new bitcoin address and stop using any previously generated addresses.

Wallets encrypted with this version of Bitcoin are written properly.

Technical note: the encrypted wallet's 'keypool' will be regenerated the first time you request a new bitcoin address; to be certain that the
new private keys are properly backed up you should:

1. Run Bitcoin and let it rewrite the wallet.dat file

2. Run it again, then ask it for a new bitcoin address.
 wxBitcoin: new address visible on main window
 bitcoind: run the 'walletpassphrase' RPC command to unlock the wallet,  then run the 'getnewaddress' RPC command.

3. If your encrypted wallet.dat may have been copied or stolen, send all of your bitcoins to the new bitcoin address.

4. Shut down Bitcoin, then backup the wallet.dat file.
 IMPORTANT: be sure to request a new bitcoin address before backing up, so that the 'keypool' is regenerated and backed up.

"Security in depth" is always a good idea, so choosing a secure location for the backup and/or encrypting the backup before uploading it is recommended. And as in previous releases, if your machine is infected by malware there are several ways an attacker might steal your bitcoins.

Thanks to Alan Reiner (etotheipi) for finding and reporting this bug.

---

Thanks to everybody who contributed code or helped test this release:

Gavin Andresen
Luke Dashjr
Pieter Wuille
Matt Corallo
cjdelisle
Wladimir J. van der Laan
Jeff Garzik
Victor Leschuk

Back on topic, it's about time for 0.6 merging, and coinbaser is still cleanly mergable. Could we get the few people who voted against it to change their votes, or at least explain them?

Any idea why my (and others') sig images don't work anymore?

Hah, good to hear.

There is whatever the community makes. I don't know of any yet

More annoying IMO, is that the images don't seem to be working anymore :/

http://eligius.st/~luke-jr/raw/5/NMC/

I encourage someone to start a poll on reducing NMC minimum payout to a better rate (perhaps the minimum required to register a domain?)

I am. It's called users phoning me. 

Seriously though, I've got a number of watchdogs setup to restart things automatically when there's a problem. Lately, the problems have been unnoticable from them, and I haven't figured out exactly how the attacker is triggering it. Instead of the pool going down, hashrate just takes a sharp dropoff (but the watchdogs are still always able to get work in a timely manner) until I restart pushpoold.

Generally, if the pool goes down, it probably won't be back until someone bothers to call me... (or IM during the day)

Test please: http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.4.1/test/

Obviously, be sure you have a wallet backup or two.

More FUD: http://www.theregister.co.uk/2011/11/15/bitcoin_flaw/

Perhaps the Microsoft research team could provide a clarification that this isn't a present issue and can easily be fixed in the future, for linking from the main page on bitcoin.org?

If I need something, I'll of course gladly buy it at a price below its real value. Same goes for bitcoins. As it is, I have plenty for the moment.

For references, this issue has been assigned CVE-2011-4447

Possibly, though it wasn't what I originally had in mind.

At least until the MtGox last hits 20 USD per BTC, or I reply to this thread (whichever is sooner). Maybe longer.

I'll sell Bitcoins at 25 USD per BTC, or 40 TBC per USD. I don't care that "everyone else" is selling Bitcoins dirt cheap. This is my offer. Take it or leave it. I'm in no rush to sell.

Edit: Also, I encourage everyone else to join me in selling no lower than this approximate price. Eventually, all the people selling dirt cheap will run out and then all selling will revert back to its proper place at $25/BTC

No, I mean the wiki page that describes a simple future-compatible scheme that the community agreed on earlier this year, and decimal trolls decided to object to months later, despite it not hurting the ability to use (in fact, it is even better for) decimal units.