Validating signatures > MitM > RCE
The Debian developer community refused to implement transport crypto for updates because “signing packages is secure enough”. Utter bullshit.
This is a quick guide on how to dramatically improve the privacy and security of your Ubuntu web server. It requires the installation of “apt-transport-tor”, an application that will allow APT transfers to occur over Tor. There is also an application called “apt-transport-https” that is already installed in Ubuntu that we’ll use.
After reviewing the existing Ubuntu updates mirrors in the USA, I found that Wikimedia has a great TLS configuration. Please contribute to the Google Doc list!
First add Tor Project’s Debian/Ubuntu repository to your system for up-to-date Tor software: https://www.torproject.org/docs/debian.html.en
Then perform the following:
sudo apt-get update sudo apt-get install apt-transport-tor sudo vim /etc/apt/sources.list
Edit “sources.list” to just use only “deb”. “deb-src” is only needed if you build from source which most people do not. You can safely delete the deb-src lines from the file. Replace all of the default Ubuntu repos with Wikimedia’s and be sure to add “tor+” before the “https”. Doing so adds end-to-end encryption via HTTPS, and it becomes Torified meaning network adversaries will have a more difficult time analyzing what software and what versions of said software are installed on your web server.
deb tor+https://mirrors.wikimedia.org/ubuntu/ xenial main restricted universe multiverse deb tor+https://mirrors.wikimedia.org/ubuntu/ xenial-updates main restricted universe multiverse deb tor+https://mirrors.wikimedia.org/ubuntu/ xenial-backports main restricted universe multiverse deb tor+https://mirrors.wikimedia.org/ubuntu/ xenial-security main restricted universe multiverse deb tor+https://deb.torproject.org/torproject.org xenial main
All your future apt-get update, upgrade, and dist-upgrade commands will now be performed over Tor and using high-grade HTTPS.
If you use UFW to manage your iptables firewall rules, and if you’re properly restricting outbound connections, below is what your config might change to. First reset your UFW rules:
sudo ufw reset
sudo ufw limit 22/tcp sudo ufw allow 443/tcp sudo ufw allow out 22/tcp sudo ufw allow out 25/tcp sudo ufw allow out 53/udp sudo ufw allow out 443/tcp sudo ufw allow out 9050/tcp sudo ufw deny out to any sudo ufw enable sudo ufw status verbose
Or with one command:
sudo ufw limit 22/tcp && sudo ufw allow 443/tcp && sudo ufw allow out 22/tcp && sudo ufw allow out 25/tcp && sudo ufw allow out 53/udp && sudo ufw allow out 443/tcp && sudo ufw allow out 9050/tcp && sudo ufw deny out to any && sudo ufw enable && sudo ufw status verbose
This UFW (iptables) rule set makes it so brute forcing SSH won’t work and allows all incoming HTTPS traffic. These rules also make it so no traffic can leave the web server unless it is SSH (22), SMTP (25), DNS (53), HTTPS (443), or Tor Socks (9050) traffic. Most web servers do not go as far as block all outbound traffic by default, but it is important in case the web server does become compromised. I would usually allow outbound HTTP (80) traffic because the default Ubuntu update repositories require HTTP. However, we will be Torifying Apt so that’s why we allow outbound 9050/tcp. If you don’t want to Torify Apt, you’ll need to allow outbound 80/tcp instead of 9050/tcp.