Silk Road forums
Discussion => Security => Topic started by: uhrwerk on May 18, 2013, 06:44 pm
-
could someone please confirm the missing support for proxy settings with the new update to v2.3.25.8 ?
-
Thread moved to the Security forum as it is not a Silk Road technical support issue.
Libertas
-
What do you mean by missing proxy settings? Onion icon -> Settings -> Network
I see the same proxy settings that have always been there. Nobody is getting paid to develop Vidalia, so it is extremely unlikely anything will change about it... until they remove it completely and integrate its features into TorBrowser
-
I can confirm that the latest version of Tor for Windows *does* have proxy (SOCKS v4a and v5) support and the proxy *is* working for me.
-
I agree the setting is there but it does open more connection than the ones one the proxy to tor.
I have not checked the ips, but if you see for yourself in the command line (start - run - "cmd" ) If you enter the command "netstat -an" it does show more connections than the ones going through the proxy for me. That has not been the case with version 2.3.25.6, only with 2.3.25.8. I also get a lot of errors trying to get the proxy setting to work. I think there is something wrong with version 2.3.25.8, or it is, to me. I am running it on windows XP.
-
Are you sure those connections belong to Tor? netstat -an doesn't show you that info. netstat -ano will show the process IDs, but then you have to find them in the list of running processes, so you might try something like TCPView. Also, have you confirmed that the outbound connections are going to Tor relays?
It's puzzling, because the Tor that's included in TBB hasn't changed since December, so it shouldn't have magically stopped working. Maybe Vidalia isn't writing the Tor options to torrc correctly? You could manually add them by shutting down TBB, opening torrc with a text editor adding either,
for Socks5 proxy: Socks5Proxy <host>:<port>
for HTTP proxy: HTTPProxy <host>:<port>
Maybe Vidalia isn't forcing Tor to reload its configuration file, so try simply restarting it first.
Also, you're not trying to run Tor over Tor are you? That's bad when connecting to clearnet sites, because your entry and exit node could be the same relay.