- Author: Jonathan M. Wilbur <[email protected]>
- Copyright Year: 2019
- License: MIT License
Sneaky Squid is a Docker container that runs a Squid proxy, which is configured to do the following, inclusively:
- Not log anything.
- Delete or replace HTTP headers that reveal information about users.
- Namely, the
User-Agent
header.
- Namely, the
- Block HTTP/S requests to tracking and analytics domains.
- Note that this blocking is very aggressive by default. Consider editing
the files in
./source/blocklists
and rebuilding if the defaults do not work for your purposes.
- Note that this blocking is very aggressive by default. Consider editing
the files in
- Block the JavaScript files commonly used in Analytics tools.
- Provide repudiatable access by intentionally not requiring authentication.
- Deploy it via Docker, Docker Compose, or Kubernetes.
- If you do not mount
/cert.pem
and/key.pem
, a new key-pair will be generated automatically for performing TLS decryption. Extract/cert.pem
from the container by runningdocker cp <container id>:/cert.pem <destination path>
, and add this certificate to your trusted roots.
- Configure your device to use it as the HTTP and HTTPS proxy.
- HTTP proxy is available on port 3128.
- HTTPS proxy is available on port 4128.
- Open up an incognito window of your web browser, preferrably on a throwaway virtual machine.
- Browse the Internet.
- When you are done, undo the proxy configuration to stop using Sneaky Squid.
- If the client is not throwaway, delete your browser history.
- If the client is not throwaway, delete the certificate from your trusted root certificates when you are done.
- HTTPS Interception
- Healthcheck
-
docker-compose.yml
- Create Kubernetes deployment.
If you would like to suggest fixes or improvements on this library, please just leave an issue on this GitHub page. If you would like to contact me for other reasons, please email me at [email protected] (My GPG Key) (My TLS Certificate). ๐