Yeah it took a while for me to find as well, Debian moved to managing alot of packages you used to install with pip. In many cases you can just prefix pip packages with python3- and find them via apt.
Yeah it took a while for me to find as well, Debian moved to managing alot of packages you used to install with pip. In many cases you can just prefix pip packages with python3- and find them via apt.
apt install python3-certbot :)
Probably not. It’s most likely automated scanning and the subdomains seem common enough to be included in wordlists. Another possibility is that the subdomains have leaked somehow, do you use LetsEncrypt? If so, the existence of your subdomains is public knowledge and can easily be picked up by bots.
I had issues until I got connectors that come with a little sleeve that you thread the wires through before putting them into the part you clamp them in. Get those if you if you haven’t already. Also get a cable tester, they are pretty cheap
Unless if you do want containers :)
So I searched a bit and this link has a few suggestions: https://www.blister-prevention.com/blogs/prevention/holes-in-the-back-of-my-shoes
TL;DR you can have a deformity on your feet called Haglunds which can worsen wear on the heel counter. There is also a possibility that you can relace your boots or use padding to reduce wear.
I would be hesitant to put a squid proxy directly on the Internet as there is a history of vulnerabilities in that software and afaik a bunch of them are yet to be fixed.
First of all I would advise against trying to bypass the security controls your school implemented, but if I hypothetically would attempt to do what you’re trying I would probably set up a haproxy on a dedicated piece of hardware, such as a raspberry pi, and expose 443 to the Internet. I would configure a simple static website to serve as default, and add a ssh backend like in this guide: https://www.haproxy.com/blog/route-ssh-connections-with-haproxy
Now you can SSH to your backend by wrapping the connection with openssl s_client. From here you can do a dynamic port forwarding, which essentially acts as a socks proxy and finally connect to that with firefox
edit: slap a tls cert on that too for good measure. Helps with hiding the ssh traffic