{"issue":{"created_at":"2011-11-23T20:18:03Z","state":"open","updated_at":"2011-11-27T22:10:31Z","user":{"gravatar_id":"6eb8809e8de066af88bc28c0eefcd734","id":1171801,"url":"https://api.github.com/users/EhVedadoOAnonimato","login":"EhVedadoOAnonimato","avatar_url":"https://secure.gravatar.com/avatar/6eb8809e8de066af88bc28c0eefcd734?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"comments":14,"body":"I noticed that my bitcoin client was getting too many connections (> 70), what's weird since I had put it behind Tor (I don't want anyone linking my IP to my transactions).\r\n\r\nI ran a \"netstat -ap | grep bitcoin\" and saw that bitcoin was bypassing my proxy configuration, opening my local port 8333 and accepting incoming connections on it. What's more troubling is that, not only it is listening when it should not, but it must be giving away my IP somehow, since all these other peers would not find me otherwise - they would try to connect to the exit-nodes, in vain. Maybe it's accessing the IRC bootstrap channel without using the proxy?\r\n\r\nI'm using version 0.5 now. I had not noticed such behavior before, so it is a regression, but I can't tell which version introduced it.","assignee":null,"id":2334094,"labels":[{"color":"FBBAAB","name":"Bug","url":"https://api.github.com/repos/bitcoin/bitcoin/labels/Bug"},{"color":"e10c02","name":"Priority High","url":"https://api.github.com/repos/bitcoin/bitcoin/labels/Priority+High"}],"number":659,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"title":"Bitcoin behind Tor still receiving connections on 8333 (identity leak) ","closed_at":null,"html_url":"https://github.com/bitcoin/bitcoin/issues/659","milestone":null,"url":"https://api.github.com/repos/bitcoin/bitcoin/issues/659"},"action":"created","comment":{"created_at":"2011-11-27T22:10:31Z","updated_at":"2011-11-27T22:10:31Z","user":{"gravatar_id":"c0d69eae553e6965038ba73dde6dead7","id":649246,"url":"https://api.github.com/users/TheBlueMatt","login":"TheBlueMatt","avatar_url":"https://secure.gravatar.com/avatar/c0d69eae553e6965038ba73dde6dead7?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"Well from what I can see we have to drop the binding port early to see if another instance is running.  I dont think it is a big deal as we now have nice locks in .bitcoin, whereas (IIRC) those weren't there when the order of BindListenPort was written by satoshi, but maybe gavin can confirm that.","id":2890578,"url":"https://api.github.com/repos/bitcoin/bitcoin/issues/comments/2890578"}}