not part of this tutorial
- nginx installation
- mariadb installation
- nextcloud installation
- how to exit VIM therefor I use nano in all commands
The first thing everyone should do before connecting to the Internet is to set up a proper firewall. Since Debian 10 (Buster), the iptables framework is replaced by the nftables framework.
To make it easier to get started, here is a short guide on how to get your firewall up and running in no time.
If you have to install Windows Server 2019 manually, you will come to the point where you ask yourself how you should install a ISO without burning the image to a physical disk and search this damned USB 2.0 External DVD drive which is covered by cobwebs in the cellar?
The Prerequisites are plain simple
- windows Iso file
- USB stick (at least 8GB)
Now that I have found a new blog software it is time to get the web server up and running. First we teach nginx a little bit about compression with gzip.
Step 1: gzip everything
By default gzip is already enabled in
/etc/nginx/nginx.conf but the important part of the configuration is commented out.
Are you sick of getting stuff you never ordered?
I had to set up a new Windows system and I remembered that the last time I tried to remove Microsoft Teams, Skype for Business and OneDrive from my Windows installation it was really annoying. So this time I had to go in a different direction. Instead of installing the complete package from office.com, I decided to install a custom package. Here is a short description how to do an office installation without the desired applications.
The problem is not that’s to easy for you to log in, the problem is that everyone else can try it too. If there are no additional mechanisms in place, such as fail2ban, an attacker will have endless time to try to guess your password or even worse the root password.
Step 1: Create a ssh key
First lets start with the key generation for your client
ssh-keygen -a 100 -t ed25519 -f ~/.ssh/example.com_id_ed25519
You have once again committed with your private mail address in a repo where you should actually use your company profile?
Does this sound familiar to you?
I know this only too well, sometimes noticed early enough but mostly my private profile ends up in the commit!
So if we can’t manage to remember to use the right config by ourselves, then this must happen automatically.