XPost: alt.comp.freeware
From: marionf@fact.com
R.Wieser wrote:
> I've got no idea what program/DLL/other you are
> talking about - and as such no idea why you call it a proxy.
For all to benefit, since I'm wired to be helpful as well as to learn,
my first experience with the Windows proxy mechanism was in the olden days
when we had to proxify tor (well before the tor browser bundle existed).
Before Firefox and before the Tor Browser Bundle, using Tor was like
assembling IKEA furniture without instructions. You had to run Tor
separately, then manually configure each app to use it as a SOCKS proxy. It
worked for some people, but I always had problems with the socks proxy.
Since those days (probably around 2001 or so) I haven't touched proxies.
Until the Epic Privacy Browser died that is, about a month or so ago.
So I built my own DIY privacy browser, which is pretty much finished.
But then I wanted to add a proxy on top of the VPN on top of the VPN.
It's slow. But it works. All using freeware that anyone can use too.
No registration necessary (as I don't use tools that need an account).
The free proxy I'm using for Windows is Psiphon
C:\software\network\proxy\psiphon\psiphon3.exe
Name: psiphon3.exe
Size: 10402576 bytes (10158 KiB)
SHA256: DB1BAF76F0333F4743919A86F35037559F9E7DA7DF14982DFC16FB8DC0BE6BE2
A proxy is an intermediary server that routes your internet traffic.
That is, instead of connecting directly to a site, your request goes
through the proxy which forwards it on your behalf for the purpose of
a. Hiding your IP address
b. Bypassing censorship
c. Adding an additional layer of anonymity (e.g., to a VPN setup)
There are different types of proxies, but mainly I seem to see only two:
A. HTTP proxies - for web traffic only
B. SOCKS proxies - which are more flexible so they're used by Tor
Windows uses 3 proxy configuration methods to accommodate different
environments, user needs & network policies. These mechanisms are:
1. Automatic Detection (WPAD)
2. Automatic Configuration Script (PAC file)
3. Manual Proxy Setup
Windows checks these settings in a layered way, for example,
1. If Auto Detect is enabled, Windows tries WPAD first.
2. If a PAC file is specified, Windows uses that next.
3. If Manual settings are entered, they override the others
Frustratingly though, each method is completely different. Sigh.
1. Automatic Detection uses WPAD to find proxy settings via DHCP or DNS
2. PAC File (Auto Script) loads a JavaScript-based file for routing logic
3. Manual Configuration sets the proxy server address & port
The script I supplied checks proxy mechanisms in the reverse order:
3. WinINET (Manual Proxy Setup)
2. WinHTTP (System Proxy) Automatic Configuration Script (PAC file)
1. PAC / Auto-Detect (Automatic Detection + PAC File) (WPAD)
The script checks them, and then sets them if they're not set.
Specifically
3. WinINET is checked first via registry keys
'ProxyEnable' and 'ProxyServer'.
2. WinHTTP is checked next using 'netsh winhttp show proxy'
1. PAC / AutoDetect is checked last via registry values for
'AutoConfigURL' and 'AutoDetect'
This order makes sense for diagnostics:
- WinINET is user-level and most commonly used.
- WinHTTP is system-level and often inherits from WinINET.
- PAC/AutoDetect is more dynamic and optional, so it's checked last.
Note the '/sync' flag explicitly copies WinINET settings into WinHTTP,
reinforcing that WinINET is the primary source and WinHTTP is secondary.
In summary, the question is simply why do 3 completely different proxy
mechanisms exist in Windows. I'm hoping to find someone who knows why.
If nobody knows more than I do, then at least everyone can learn from my
recent experience using Psiphon freeware with Microsoft Windows browsers.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
