j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMw<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=461.msg5383#msg5383">Quote from: satoshi on July 23, 2010, 08:39:03 PM</a></div><div class="quote">BTW, I haven't tested it, but I hope having rpcpassword= in the conf file is valid. It's only if you use -server or -daemon or bitcoind that it should fail with a warning. If it doesn't need the password, it should be fine. Is that right?<br/></div>Yes, that's right, rpcpassword is only required if you use -server or -daemon or bitcoind (I just tested to be sure).<br/><br/>RE: what if the programmer can't figure out how to make their legacy COBOL code do HTTP authentication?<br/>Then I think another config file setting to explicitly turn off RPC authentication would be better than a magical "if you set a blank rpcpassword then that turns off authentication." But I wouldn't implement that until somebody really does have a problem or until we have more than one way of doing the authentication (maybe https someday...).<br/><br/>lachesis: is supporting HTTP Basic Authentication a problem for you?<br/></div> text/html
https://whatsonchain.com/tx/eee2eecf9a353ea35ee8013edb1bcb8ff642930d2fc09ce04de3daa74592b9d4