Can anyone from India confirm if this proxy server [1] is enough to bypass the block?
Basically it is a proxy that alters HTTPS traffic to prevent DPI systems from detecting the domain during the TLS handshake. At least in Spain it works for me to bypass the blocking of the major ISPs [2].
Can you explain in detail how this is supposed to work? Am I supposed to run this (Docker here) on my local server or on a remote server that the block is not affecting??
You can of course set this up manually outside Docker, I provide this image so that you can easily have a preconfigured installation with VNC, RDP, bind shell and a Samba server.
During the installation I add Netcat to have a bind shell, this way you can get a CMD shell from Linux using the "vmshell" command included in the image.
So yes, technically it's backdoored but only for yourself :)
Effectively this is done as a POC, don't expect any security on a machine running Windows 2000 nowadays.
Regarding legality, I hope that Microsoft doesn't claim any rights, since the Windows 2000 image has been published in WinWorld for years without issues.
I'd guess that the "don't expect any security" comment above meant exactly that. Not that you should forgo security, but that you should expect this to provide no security at all.
Some other comments mention browsing with IE5. You should expect that to provide no security either.
The ISO is downloaded from WinWorld, which is a website dedicated to archiving old software, it's certainly community maintained but at least gets some scrutiny. I also searched the checksum and it matches with other sources, but as there is no longer an official Microsoft source you can never be entirely sure.
I've done my best to confirm the legitimacy but if anyone has an original CD it would be awesome if they could confirm it.
My suggestion is to not embed third party urls for infringing software.. that makes you a target. Inside leave that variable empty and make suggestions on where one could find the media whether it’s the original or from questionable third party websites.
This is how popular emulators survived the 90s, they emulate the bios but force you to find the firmware yourself. Even if it means downloading from an unknown source without a supply chain and running unknown code on your computer. The emulator and author are in the clear
What? Can you elaborate? If I spin this up in a container, even though it has access to the internet, how am I owned within a few minutes, given that my firewall is in place and I don't expose any port of this container to the internet?
In the case that someone has any trouble configuring WireGuard, I would like to share my automatic deployment of WireGuard and Unbound with full IPv4 and IPv6 support with Packer and Terraform in Hetzner Cloud (although it can be easily adapted to other providers) [1].
In the case that no automatic deployment is necessary, it may also be useful to look directly at the WireGuard configuration [2]. Since WireGuard supports scripts in "PostUp" and "PostDown", I have automated the configuration of iptables, including some useful rules to redirect 53/UDP port traffic from the public interface to WireGuard, which helps in some cases to bypass some firewalls.
- https://web.archive.org/web/20260605175351/https://github.co...
- https://web.archive.org/web/20260605175320/https://github.co...
- https://web.archive.org/web/20260605175256/https://github.co...
reply