Terminology: revoked means the issuer of the certificate has decided that the certificate should not be trusted anymore even though it is still valid.

If a attacker gets access to a certificates key, they can impersonate the server until the validity period of the cert runs out or it is revoked by the CA. However … revocation doesn’t work. The revocation lists arent checked by most clients so a stolen cert will be accepted potentially for a very long time.

The second argument for shorter certs is adoption of new technology so certs with bad cryptographic algorithms are circled out quicker.

And third argument is: if the validity is so short you don’t want to change the certs manually and automate the process, you can never forget and let your certs expire.

We will probably get to a point of single day certs or even one cert per connection eventually and every step will be saver than before (until we get to single use certs which will probably fuck over privacy)

One reason for the short certs is to push faster adoption of new technology. Yes that’s about new cryptography in the certs but if you still change all your certs by hand maybe you need to be forced …

You don’t need something ever. Sometimes you just want something because the alternative is realy bad. I don’t need to eat. I want to eat because I don’t want to starve.

I want to watch a movie with my partner at the agrees time because otherwise they will be mad. I want to access my digitalized documents to send a letter in time because otherwise I will have to pay late fees. I want to access my gameserver because that’s the one time a week I get to have fun with my friends from my college time.

There are many situations where I’d rather do the thing I want instead of doing maintenance.

There is still a good reason to know about problems early. Without any monitoring you will find out about problems exactly in that moment when you what to use the service that doesn’t work. Sometimes you need something quick and you don’t have time to debug and fix in that moment. If you get an alert early you can decide to fix it right away or in a few hours or tomorrow.

Not like the whole video goes from 1080p to 720p or something but single bits of the drive will fails over time. If that bit is part of your video file, one pixel of one frame will be the wrong color/black. If multiple bits close to each other fail you might get a video stutter. If even more fail your video player will not play the video at all (or just stop playing at the place of the errors).

That is the smallest scale of self hosting. The server and the client are the same device. It is also the most insecure way as you probably don’t have any backups and very limited storage space.

Actually self hosting is the next step when you decide you want 5+ TB of data and have it automatically create backups. Digital storage media degrade pretty quickly and if you just have your movies on a hard drive in your computer, after 5-10 years you might start to lose quality or some files completely.

You most likely pay for a maximum CPU capacity and your Server cant go above that no matter what you run. Your vps provider doesn’t care what that CPU power is used for.

However with limited resources, the tarpit might use up all CPU power and the rest of the webserver will crawl to a halt.

wg-quick creates a systemd service for each wireguard config you have. So if you set up a tunel called wg0, you should be able to run ‘sudo systemctl enable wg-quick@wg0’ This will make your tunnel connect on every boot. I have the same setup on my proxmox, so i can reach certain services of my homelab proxied through a root server (the other end of the wireguard tunnel)

Decryption is not related to root permission.

If the ENCRYPTED drive is mounted to the container, then the container can decrypt it.

If the DECRYPTED drive is mounted to the container, then the container never knows it was encrypted in the first place.

Second case is easier BTW. Just mount the drive on your host, type in the encryption password and you get a new, unencrypted drive. Specify this new drive in your docker compose/docker file.

Generally, Linux Servers are best administered from a command line. At least in the beginning to set everything up. In turn they are faster on lower hardware as they dont even have a graphical desktop at all so need less resources. You could of course install a windows server OS. They can be fully administered through Remote Desktop and a GUI.

There are multiple projects to make self hosting more accessible (like casaOS). They automate many steps of the setup and then offer you a webUI for further steps. Maybe have a look here https://github.com/awesome-selfhosted/awesome-selfhosted?tab=readme-ov-file#self-hosting-solutions