j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMÁ<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1291.msg14352#msg14352">Quote from: doublec on September 28, 2010, 12:51:22 AM</a></div><div class="quote"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1291.msg14263#msg14263">Quote from: Marko on September 27, 2010, 04:50:25 PM</a></div><div class="quote">I read the wiki and it says the interface only accepts requests from 127.0.0.1. Is this still the case? Is there a setting to override this?<br/></div><br/>This is still the case and I don't believe there is a setting to override it. It's hardcoded in the source. Instead of writing a 'proxy' app you can use SSH to tunnel. For example, if your bitcoin instance is running on 'example.com' and that machine is running an ssh server, you can tunnel to it from another machine with:<br/><br/>ssh -N example.com -L 9481:localhost:9481<br/><br/>Now you can use the RPC interface on your local machine to port 9481 and it will be tunnelled over an encrypted SSH session to the machine running the bitcoin RPC server.<br/><br/>You want to encrypt the connection because the JSON-RPC password is sent in clear text (it's actually base 64 encoded but basically it's the equivalent of clear text).<br/></div><br/>Can you compile your own bitcoin? The latest svn has an option to allow binding to other interfaces, not just localhost. If not the next version (0.3.13) is supposed to have that.</div> text/html
https://whatsonchain.com/tx/43f3ae616d3c5e224f511a3464c7d652206d2c7b8b44eaadb50412ef4e12a8a3