MultiProxy public forum
| From | Message |
Mithridates
1/22/2001
19:38:56 |
 Subject: Improved chaining method for anonymous surfing
203.77.126.62--->
Message:
I will expound upon my previous post regarding the use of wingate proxies for anonymity.
I experimented with a new method I derived, and found a way to perhaps help one's statistical chance of not being tracked if someone on the other end wished to do so.
I tunneled my browser through a socks proxy on port 1080, and when I checked my anonymity on several different sites, the IP of the socks proxy was given. I then tunneled multiproxy itself through a different socks proxy, thus making my HTTP internet connection flow through 2 non-logging socks proxies and 1 non-transparent HTTP proxy (the one multiproxy used) on port 80. This make 3 proxies one must go through in order to locate my real ISP.
So to repeat: Open your browser with a socks proxy. Then let multiproxy open using a different socks proxy, then let it perform its routine check of the HTTP proxies utilizing the socks connection. Once it is finished, just use multiproxy like you normally would, but instead of surfing through one HTTP proxy, you are now surfing through 2 socks proxies and 1 HTTP proxy, thus increasing your chances of not being tracked.
This is the best method I know of for remaining anonymous on a windows platform since many wingate's on port 23 do not log their servers.
Enjoy
|
someguy
1/22/2001
20:03:53 | RE: Improved chaining method for anonymous surfing
207.193.12.143--->
Message:
i understand most of what you are saying but what about the proxies for http and secure etc. for my browser
i am a little confused
|
S
1/22/2001
20:26:24 | RE: Improved chaining method for anonymous surfing
212.44.60.50--->
Message:
This is excellent info. I have two Q's for you:
1) Would you say the time of the delay between requests and receipts using the above config is less than, greater than, or equal to a similarily config'd HTTP daisychain?
2) I once read that socks ports are the most "vulnerable" protocols on the Net. Can you explain why this would be, or not, if untrue?
Now briefly for SG: Secure is HTTPS, same as HTTP but utilizes a tunnel (SSL or TSL) for passing encrypted data back and forth.
|
James
1/23/2001
07:42:44 | RE: Improved chaining method for anonymous surfing
205.200.28.78--->
Message:
Hi,
I am not familiar with socks and I find your post too confusing.
Can you please give an example what values you put where? I mean like
1) in browser set connection to SOCKS#1.
2) in MP set (is it Options or Proxy List?) to SOCKS#2
etc.
(I don't get where is the 2 SOCKS are chained)
See, I am slow :(
|
Mithridates
1/23/2001
14:32:21 | RE: Improved chaining method for anonymous surfing
202.97.30.181--->
Message:
I am going to try to answer everyone's questions in this post.
Someguy,
The secure internet protocol is generally referred to as HTTPS, which is nothing but a method of encrypting data from the target site back through the cyber path to your computer.
In order to use the method I outlined with HTTPS, you would simply find a working non-transparent HTTPS proxy and put it inside the MP list (preferably by itself.) Then open ur broswer and MP with 2 seperate socks proxies.
S,
To answer the first question:
I suppose the speed would depend on the resources of the server the socks is running on. If it is a wingate on port 23, more than likely it is being ran by an individual with a regular PC, perhaps with a broadband connection. It is possible that socks proxies may be faster than regular HTTP proxies because it is likely that far fewer people are using the bandwith of a socks proxy because few people realize you can use the socks protocol for web surfing. More than likely, the person running the wingate doesn't even know you are hitting his server. If you have a broadband connection at your home, I wouldn't worry about a few milliseconds of latency. However, with my dial-up connection I can tell a difference while surfing through my chain of proxies. It is noticeably slower, but worth it if you need anonymity.
I have never personally ran a wingate server, but I suppose why many people believe they are insecure is because it might be possible for someone else on the server to view your data packets much more easily than they could on an HTTP protocol. But I wouldn't worry about this because if the wingate doesn't log, it is unlikely anyone even knows you are there.
Also, so many people who run socks servers don't realize they are giving hackers an easy avenue for carrying out hack attempts through their servers. I suppose their ease of entrance is one reason people think they aren't secure.
And for James:
I will spoon feed him with another explanation of the method I derived last night.
James, first you need to download a utility to tunnell ANY of your Winsock apps through a socks server.. SocksCap is the one I use.
Next, find several working proxies operating on port 23. Once you find one, configure SocksCap to use it, except enter the port as port 1080, not port 23. Then open your browser. You should now be connected to the web through that socks server.
Now, with your browser still open, change the proxy setting in SocksCap to a different socks server. Now, open multiproxy with this new socks server. Multiproxy should now be connecting to its proxy list through this second socks server. (Note: I have found that when checking the HTTP proxies through a socks connection, MP will not display the IP addresses of the proxies in it's list)
Be sure your browser's proxy configurations are set up to use multiproxy. Now, begin surfing the web. The first socks proxy will send the initial request to your browser, then your browser will send the request to MP, but it first must pass through the socks server which was used to open MP. Then that socks server will send the request to the HTTP server inside of MP, thus making your internet connection go through 3 proxies - two socks and one HTTP. Good luck!
|
someguy
1/23/2001
15:11:42 | RE: Improved chaining method for anonymous surfing
207.193.12.18--->
Message:
thanx guy
|
James
1/23/2001
15:57:59 | RE: Improved chaining method for anonymous surfing
195.112.4.250--->
Message:
WOW, I am impressed.
I guess I need to learn about SOCKS and the program you mentioned. That was my missing link.
I guess I try it some time soon.
thanks.
|
S
1/24/2001
00:17:00 | RE: Improved chaining method for anonymous surfing
216.139.202.72--->
Message:
Yes MD, thank you.
|
jazzie142
1/30/2001
21:29:43 | RE: Improved chaining method for anonymous surfing
204.196.123.2--->
Message:
where do i find a proxy operating on port 23
|
|
Post a reply to this message:
|
|
