You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
180 lines
7.3 KiB
HTML
180 lines
7.3 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="utf-8">
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
<meta name="description" content="A new step for aney.co.uk, there's now a blog.">
|
|
<meta name="keywords" content="Blog, articles, news">
|
|
<meta name="author" content="Nathan (Aney) Steel">
|
|
<meta name="theme-color" content="white">
|
|
<meta name="theme-color" content="black">
|
|
<link rel="stylesheet" type="text/css" href="/main.css">
|
|
<link rel="icon" type="image/png" href="/images/favicon.svg">
|
|
<title>Debian Server Setup</title>
|
|
</head>
|
|
|
|
<body>
|
|
<header>
|
|
<h1>Debian Server Setup</h1>
|
|
<hr/>
|
|
<nav>
|
|
<a href="/">home</a>
|
|
<a href="/equipment.html">equipment</a>
|
|
<a href="/projects.html">projects</a>
|
|
<a href="/blog/">blog</a>
|
|
<a href="/sitemap.html">misc</a>
|
|
<a href="/support.html">support</a>
|
|
</nav>
|
|
<hr/>
|
|
</header>
|
|
|
|
<main>
|
|
<section>
|
|
<p>This section assumes you have a fresh Debian 11 install on a server (either physical or VPS)</p>
|
|
<p>It will cover installing the essentials for access, and basic security so you don't need to worry in the future. This section may seem a little daunting for a first-time linux user, but most of it is copy/paste, hopefully with enough description to understand what is being done. Just remember not to copy the $/root$ they're there to show what user/directory we're in. </p>
|
|
</section>
|
|
|
|
<section>
|
|
<p>This first section will be done on the physical PC, or on the VPS via their website, or SSH'd as root if that's the option given.</p>
|
|
|
|
<h2>Update the OS</h2>
|
|
<p>Even with a fresh install of Debian from the latest ISO, there may be some updates you're missing, and it's a good idea to have these, especially in case they're security updates.</p>>
|
|
<pre>
|
|
<code>
|
|
root$ apt update && apt upgrade
|
|
</code>
|
|
</pre>
|
|
|
|
<h2>Install essential packages</h2>
|
|
<p>These are packages that are needed for accessing, and controlling the server</p>
|
|
<pre>
|
|
<code>
|
|
root$ apt install sudo ssh
|
|
</code>
|
|
</pre>
|
|
<h3>Some useful packages too</h3>
|
|
<pre>
|
|
<code>
|
|
root$ apt install vim htop wget curl tmux
|
|
</code>
|
|
</pre>
|
|
|
|
<h2>Add a user, and give super user privilleges</h2>
|
|
<p>You want to avoid using root as much as possible in regular use, so a new user for yourself is a must</p>
|
|
<pre>
|
|
<code>
|
|
root$ adduser <USERNAME>
|
|
root$ usermod -aG sudo <USERNAME>
|
|
</code>
|
|
</pre>
|
|
<p>*replace <USERNAME> with the user you want to create, e.g. nathan</p>
|
|
|
|
<h2>(Local server) Set static IP</h2>
|
|
<p>If the server is a physical PC in your home you will need to set a static IP, otherwise your router could assign a differnent IP on reboot, and this would mess with port forwarding, and internal DNS.</p>
|
|
|
|
<h2>Secure ssh</h2>
|
|
<p>Although this is optional, I recommend it, as SSH (secure shell) will be the primary means of access to the server.</p>
|
|
<pre>
|
|
<code>
|
|
root$ vim /etc/ssh/sshd_config
|
|
</code>
|
|
</pre>
|
|
<p>Within the editor you will need to search for <strong>PermitRootLogin</strong> and set it to <strong>no</strong>, this prevents ssh as root</p>
|
|
<p>Search for <strong>Port</strong> and set it to a different port to 22, a port over 1024 prevents basic nmap scans, and therefor a lot of bruteforcing, so let's go with 2020 so it's easy to remember</p>
|
|
<p>Below the <strong>Port</strong> line, add a new line with <strong>Protocol 2</strong> this enables ssh2, which is more secure</p>
|
|
<p>(Optional) Comment/Add a <strong>#<strong> to the beginning of the <strong>passwordlogin</strong> line. This will prevent sshing to the server from any PC that doesn't have it's SSH key on the server already. I recommend only doing this if your sshkeys are on the server, or you're comfortable adding them.</p>
|
|
<pre>
|
|
<code>
|
|
root$ systemctl reload sshd
|
|
</code>
|
|
</pre>
|
|
<p>This reloads the ssh daemon, and enables all the changes we've made</p>
|
|
|
|
<h2>Setup UFW</h2>
|
|
<p>UFW (Uncomplicated Firewall) is a simple to use firewall, that can be used to easily open/close ports on your server.</p>
|
|
<p>We'll install ufw, deny access inwards to all ports, but allow our server to access any ports outwards. We will then manually allow inwards traffic to the SSH port we set, in this case 2020</p>
|
|
<pre>
|
|
<code>
|
|
root$ apt install ufw
|
|
root$ ufw deny incoming
|
|
root$ ufw allow outgoing
|
|
root$ ufw allow 2020
|
|
root$ ufw enable
|
|
</code>
|
|
</pre>
|
|
<p>If there are any other ports that need to be opened in the future this can be done with:</p>
|
|
<pre>
|
|
<code>
|
|
root$ ufw allow <PORT>
|
|
</code>
|
|
or
|
|
<code>
|
|
root$ sudo ufw allow <PORT>
|
|
</code>
|
|
</pre>
|
|
|
|
<h2>Set hostname</h2>
|
|
<p>Setting the name for a server is an important step, but the name doesn't need to be serious</p>
|
|
<pre>
|
|
<code>
|
|
root$ vim /etc/hosts
|
|
root$ vim /etc/hostname
|
|
</code>
|
|
</pre>
|
|
<p>Within both of these files the hostname should be changed to the same thing</p>
|
|
|
|
</section>
|
|
|
|
<section>
|
|
<p>This next section can be done via a terminal, or an SSH client e.g. PuTTY for Windowss. For the sake of the guide, this assume you're using a Unix terminal</p>
|
|
<h2>Create an SSH key</h2>
|
|
<p>We'll create an ed25519 ssh-key, as it's more secure, and performant than the defaultrsa</p>
|
|
<pre>
|
|
<code>
|
|
$ ssh-keygen -t ed25519
|
|
</code>
|
|
</pre>
|
|
<h2>SSH into the server</h2>
|
|
<p>This is a two part section, and I recommend using this every time you SSH into a server from a new PC</p>
|
|
<pre>
|
|
<code>
|
|
$ ssh <USER>@<HOST> -p 2020
|
|
</code>
|
|
</pre>
|
|
<p>This will likely display a message asking to verify the key for the server. This is to prevent man-in-the-middle attacks, so I reccommend verifying this whenever asked.</p>
|
|
<p>To check the key for the server, you need to run this command on the server.</p>
|
|
<pre>
|
|
<code>
|
|
$ ssh-keygen -l -f /etc/ssh/ssh_host_<KEY>_key.pub
|
|
</code>
|
|
</pre>
|
|
<p>Replace <KEY> with the key the message is asking about. Then if key the server shows matches that on your PC you are SSHing from, type <strong>yes</strong> and hit enter</p>
|
|
|
|
<h2>TODO:(Optional) Fail2Ban</h2>
|
|
|
|
<h2>TODO:(Optional) Unattended Upgrades</h2>
|
|
<p>Updates to a server typically want to be done by a human in case things go wrong, but smaller updates can be set to be done automatically</p>
|
|
|
|
<h2>TODO:(Optional) Setup User preferences</h2>
|
|
<p>These are a few things I personally like to have on a basic server</p>
|
|
<h3>Vi mode bash</h3>
|
|
<h3>Aliases</h3>
|
|
<h3>Ctrl-L clear-screen</h3>
|
|
<h3>BashRC PS1</h3>
|
|
|
|
<h2>Server maintance notes</h2>
|
|
<p>Keep the server up-to date as much as possible</p>
|
|
<p>Only install things that you need. If this is a server for learning, half ignore this, but for production servers only install services, and make changes that are required.</p>
|
|
<p>
|
|
|
|
</section>
|
|
</main>
|
|
|
|
<footer>
|
|
<hr/>
|
|
<p>Written by <a href="http://www.aney.co.uk" target="_blank" rel="noopener">@aney</a> with <a href="https://danluu.com/web-bloat/" target="_blank" rel="noopener">web bloat</a> in mind | <a href="https://github.com/Aney/website" target="_blank" rel="noopener">Source Code</a></p>
|
|
</footer>
|
|
</body>
|
|
</html>
|
|
|