Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.comp.freeware    |    Generic free software discussions    |    39,988 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 39,382 of 39,988    |
|    Marion to All    |
|    Re: Tutorial: FOSS ProxyBridge & TOR SOC    |
|    26 Oct 25 14:25:30    |
      From: mariond@facts.com              This is just too easy to chain encryptions in a ladder-like sequence       using only freeware (there is no charge and no registration for anything!)              a. binary -> proxifier -> proxy server -> VPN server -> ISP -> Internet       b. Internet -> VPN server -> proxy server -> proxifier -> binary              This is just to let people know that in the past I had asked this newsgroup       if you can ladder encryption, and it turns out, that you certainly can!              Woo hoo!       It has been years that I had wanted to do this, which everyone said (at the       time I originally asked anyway) that it couldn't easily be done.              And, yet, it's almost trivial to accomplish!              What I've successfully sequenced in series is the following encryptions:       1. Any Windows binary executable -> generates traffic       2. Proxifier -> intercepts app TCP/UDP & forces it through proxy       3. Proxy server -> wraps traffic & forwards via its own tunnel       4. VPN server -> encapsulates proxy traffic inside VPN tunnel       5. ISP -> sees only encrypted tunnel to VPN server       6. Internet -> sees traffic only from VPN server              Here's how to accomplish this nested encryption. Easy Peasy!       A. Connect to your ISP (I'm on WISP which is free & no registration)       B. Start your free public no-registration VPN service       C. Start your free public no-registration PROXY service       D. Start your free public no-registration proxifier service       E. Start your free public no-registration Windows binary       F. Point that windows binary (e.g., browser.exe) to the Internet URI              Here is what each hop can infer about you when looking backward:       (Internet IP -> ISP IP -> VPN IP -> PROXY IP -> proxifier -> binary)              6. Internet domain -> sees only the VPN exit IP address       5. ISP -> sees your IP & that you connect to VPN, nothing beyond       4. VPN server -> sees your real IP & that you connected to a proxy       3. Proxy server -> sees only the VPN exit IP & proxied app traffic       2. Proxifier -> knows which app is forced through the proxy       1. Windows binary -> just thinks it's talking to the Internet              Woo hoo! It can be done!       --       Note I get my WISP for free also, but most people won't be able to do that.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca