You could do worse than using yaml for the settings I was researching config file formats, here’s a comparison. YAML is massive. I’m not sure there’s a lightweight easy to build library we can integrate into our project. Seems overkill. JSON is tempting and I’m inclined to like it, but […]
Read moreCategory: Bitcoin Talk
Re: JSON-RPC password
If you’re using another JSON-RPC client that you wrote you can take care to protect the password, but using the bitcoin binary as the client and passing the password on the command line has the same issue as starting the daemon with it. It’s still visible to every user that […]
Read moreRe: They want to delete the Wikipedia article
http://en.wikipedia.org/wiki/Bitcoin This article is being considered for deletion in accordance with Wikipedia’s deletion policy. Please share your thoughts on the matter at this article’s entry on the Articles for deletion page. This article needs references that appear in reliable third-party publications. Primary sources or sources affiliated with the subject are […]
Read moreRe: JSON-RPC password
The Transmission BitTorrent client does authenticated JSON-RPC; see “Remote Control” section of: https://trac.transmissionbt.com/wiki/ConfigurationParameters E.g. setting.json file might look like: Code: { “rpc-enabled”:1 “rpc-authentication-required”: 1, “rpc-password”: “xxxxxxxxxx”, “rpc-port”: 9091, “rpc-username”: “xxxxxxxxxx”, “rpc-whitelist-enabled”:1 “rpc-whitelist”:”127.0.0.1,192.168.*.*” } It uses HTTP ‘basic’ authentication (Authorization: basic base64(username:password) in the HTTP headers). So you drop a settings […]
Read moreWarning: don’t use -server or bitcoind where you web browse (v0.3.2 and lower)
Don’t use the -server or -daemon switch or run bitcoind on a machine where you use a web browser. It opens port 8332 on 127.0.0.1, the local loopback address, and you wouldn’t think that web browsers could cross-site access it, but it is possible. We’re working on a release soon […]
Read moreRe: JSON-RPC password
I guess it’s ok for remotely doing it but if your concern is that someone else on the same unix machine can steal your bitcoins this still doesn’t help because they can see your command line in /proc, top, ps etc. It could read the password on stdin or use […]
Read moreRe: Did block generation crawl to a halt?
I created a realtime graph of the current block generation speed here; http://titania.smutfairy.com/~rm/time.gif Nice graph! A moving average to smooth it out would be nice. http://nullvoid.org/bitcoin/statistix.php says 212 blocks in the last 24 hours, or 8.8 per hour. Related posts: e: 28 days without generation, i have 4200khash/s Hi. I know […]
Read moreRe: Nenolod, the guy that wants to prove Bitcoin doesn’t work.
What amount does one have to send to incur a transaction fee though? I’ve send some large amounts around myself and never saw a fee? Typically, over 25,000 BTC. Related posts: Re: Nenolod, the guy that wants to prove Bitcoin doesn’t work. So this guy has about 1000 cores generating […]
Read moreRe: MSVC build & SHA-256
I’ve managed to set up dependencies and build bitcoin with MS Visual C++ 2008 Express Edition. I’ll give 2010 a try at some time. There is a custom allocator class in serialize.h, secure_allocator, that fails to build with non-debug runtime selected. It is my understanding allocator classes require a template […]
Read moreJSON-RPC password
I uploaded to SVN my changes to add a password to JSON-RPC. If you’re set up to build, please test it. The -server switch is replaced with -rpcpw=<password>, which is also used with bitcoind. bitcoin -rpcpw=<password> — runs with JSON-RPC port open bitcoind -rpcpw=<password> — daemon with password […]
Read more