![\"\"](\"https:\/\/lowtek.ca\/roo\/wp-content\/uploads\/2019\/02\/ssd-500x160.png\")
<\/p>\n<\/p>\n
Way back in late 2016 I started building a new server<\/a> to replace my aging server that runs this website, email, etc. I’m still slowly working towards actually swapping all of the services I run to the new hardware, a process slowed by the fact that I’m trying to refactor everything to be container based – and that I simply don’t seem to have a lot of free time to hack on these things. This has been complicated by the original motherboard failing to work, and my desire to upgrade the SSD<\/a> to a larger one.<\/p>\n Originally I had a 60GB SSD, which I got at a great price (about $60 if I recall). Today SSD prices have fallen through the floor, making it seem sensible to start building 1TB raid arrays out of (highly reliable) SSDs. A little before Christmas I picked up a 120GB Kingston SSD<\/a> for around $30. Clearly it was time to do an upgrade.<\/p>\n Back in 2016, the right choice was Ubuntu 16.04<\/a>, in 2019 the right version is 18.04 LTS<\/a>. Now while I haven’t moved all the services I need to the new server (in fact, I’ve moved very few) — there are some services which do run on the new server and my infrastructure does rely on them. This means that I want to minimize the downtime of the new server, while still achieving a full clean install.<\/p>\n Taking the server offline for ‘hours’ seemed like a bad idea, however since my desktop is a similar enough machine to the new server hardware it seemed like a good idea to use it to build the new OS on the new SSD. In fact, my bright idea was to do the install with the new SSD inside of a USB enclosure.<\/p>\n Things went smoothly, download 18.04.02, create a bootable USB stick, put SSD into a drive enclosure, boot with USB stick and do an install to the external SSD. Initially I picked a single snap, the docker stuff – I later changed my mind about this and re-did the install. The shell\/curses based installer was new to me – but easy to use. The only option I picked was to pre-install OpenSSH server because of course I want one of those.<\/p>\n Attempting to boot from the newly installed SSD just didn’t work. It was hanging my hardware just after POST. This was very weird. Removing the SSD from the enclosure and doing a direct SATA connection worked fine – and it proved that the install was good to go.<\/p>\n For the next part, I’m using my old OS setup post<\/a> as a reference.<\/p>\n Either 18.04.02 is recent enough, or the install has changed – but I didn’t need to do<\/p>\n since doing the above made no changes to the system as installed. Still, it doesn’t hurt to make sure you are current.<\/p>\n Of course, we still want fail2ban<\/p>\n I didn’t create a new SSH key, but copied in the keys from the old system. I did need to create the .ssh directory.<\/p>\n Once you’ve copied in the id_rsa files, don’t forget to create the authorized_keys file<\/p>\n It’s a good idea now to verify that we can access the machine via ssh. Once we know we can, let’s go make ssh more secure by blocking password based authentication. The password is still useful to have for physical (console) logins.<\/p>\n Let’s also setup a firewall (ufw<\/a>)<\/p>\n Now as we will almost exclusively be using docker to host things, docker will be managing the iptables for us in parallel to ufw. So strictly speaking we don’t need 80 or 443 enabled because docker will do that when we need to. I did also discover that ufw has comments<\/a> you can add to each rule – making a nice way to know why you opened (or closed) a port.<\/p>\n Staying on the security topic, let’s install logwatch. This requires a mail system – and as we don’t want postfix because that will interfere with the plan to put email in a docker container.. we are going to use nullmailer setup to send email to our mail server (hosted on the old server until we migrate).<\/p>\n Don’t forget to configure logwatch to email us daily<\/p>\n For docker<\/a> we’re going to hook up to the docker.com repositories and install the CE version. To do this we need some additional support added to our base install.<\/p>\n We can now install docker.<\/p>\n I also like to be able to run docker as ‘me’ vs needing to sudo for every command<\/p>\n Don’t forget that you need to logout\/login to have your shell environment pick up the permissions to do this.<\/p>\n A few more annoyances we’re going to address. Needing my password to sudo is inconvenient. I’m willing to trade off some security for making this more convenient – however, be aware we are making a trade-off here.<\/p>\n TIL visudo is the safe way to edit sudoers https:\/\/t.co\/qop34V5zxf<\/a> .. and yes, I'm currently locked out of my linux box<\/p>\n — Roo (@andrew_low) February 16, 2019<\/a><\/p><\/blockquote>\n$ sudo apt-get update\r\n$ sudo apt-get upgrade<\/pre>\n
$ sudo apt-get install fail2ban<\/pre>\n
$ mkdir .ssh\r\n$ chmod 700 .ssh<\/pre>\n
cp id_rsa.pub authorized_keys\r\nchmod 400 authorized_keys<\/pre>\n
$ vi\u00a0\/etc\/ssh\/sshd_config\r\n\r\n# Change to no to disable tunnelled clear text passwords\r\nPasswordAuthentication no<\/pre>\n
$ sudo ufw allow 22\r\n$ sudo ufw allow 80\r\n$ sudo ufw allow 443\r\n$ sudo ufw enable<\/pre>\n
$ sudo apt-get install nullmailer\r\n$ sudo apt-get install logwatch<\/pre>\n
$ vi\u00a0\/etc\/cron.daily\/00logwatch\r\n\r\n# execute\r\n\/usr\/sbin\/logwatch --output mail --mailto myid@lowtek.ca --detail high<\/pre>\n
# things we need to make the install go smoothly\r\nsudo apt-get install \\\r\n apt-transport-https \\\r\n ca-certificates \\\r\n curl \\\r\n gnupg-agent \\\r\n software-properties-common\r\n\r\n# add the key from docker.com\r\ncurl -fsSL https:\/\/download.docker.com\/linux\/ubuntu\/gpg | sudo apt-key add -\r\n\r\n# add the repository\r\nsudo add-apt-repository \\\r\n \"deb [arch=amd64] https:\/\/download.docker.com\/linux\/ubuntu \\\r\n $(lsb_release -cs) \\\r\n stable\"\r\n\r\n# update apt\r\nsudo apt-get update<\/pre>\n
$ sudo apt-get install docker-ce docker-ce-cli containerd.io<\/pre>\n
$ sudo gpasswd -a ${USER} docker\r\n$ sudo service docker restart<\/pre>\n\n