Lacking access to change addresses was a bit of a hole in the raw transaction functionality, I've found.
It was named "getraw..." to emphasize this is not for normal use.
The current definition of a change address, AFAICS: in the wallet, but not address book.
I wonder if createrawtransaction shouldn't support something like {"1aaaa":1.0,"change":1.0} and {"1Aaaa":1.0,"fee":1.0} the latter failing if the inputs are not known to it.
Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/e5e9904c1c87fcdddf01e563ffe28cc56aea4f29 for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.
@gmaxwell I'd like to see such "magic" targets (fee, change) as well. I suppose the logic would be: if change is specified, it's replaced by a random change address pulled (and marked) in your wallet. If fee is present, it must be the exact different between inputs and outputs.
Another @sipa +1
This pull: looks good to me, ACK.
ACK.