lorentz

It is not just a matter of how many ports are open. It is about the attack surface. You can have a single 443 open with the best reverse proxy, but if you have a crappy app behind which allows remote code execution you are fucked no matter what.

Each port open exposes one or more services on internet. You have to decide how much you trust each of these services to be secure and how much you trust your password.

While we can agree that SSH is a very safe service, if you allow password login for root and the password is "root" the first scanner that passes will get control of your server.

As other mentioned, having everything behind a vpn is the best way to reduce the attack surface: vpn software is usually written with safety in mind so you reduce the risk of zero days attacks. Also many vpn use certificates to authenticate the user, making guessing access virtually impossible.

Ikea and Lidl zigbee work well for me and are reasonably cheap. Ikea's look a little better, but I have only one because it is a pretty recent product.

I have automated it with a small initramfs script which has half password and download the other half from internet. My threat model is to protect from a random thief. So they should connect it to a network similar to mine (same netmask and gateway) and boot it before I can remove the half key from internet.

some security which is on my TODO list is: allow fetching the half key only from my home IP and add some sort of alert for when it is fetched.

The really important things (essentially only photos) are backed up on a different USB drive and remotely on backblaze. Around one terabyte cost 2-3$ per month (you pay by operation, so it depends also by how frequently you trigger the backup). You want to search for "cold storage" which is the name for cloud storage unfrequently accessed (in other words, more storage than bandwidth). As a bonus, if you use rclone you can encrypt your data before sending it to the cloud.

Backup and encryption. encryption prevents the thief to see my data, backup allows me to make a new server. Furthermore, as other pointed out, I don't expect that a common thief will see a lot of value in a small black box on top of a shelf

I remember reading a post on mastodon where it was explained that no mother board validates the secure boot keys expiration dates otherwise it wouldn't boot the first time the BIOS battery gets empty and the internal clock gets reset. The post was written well and was citing some sources. But I didn't try to verify these assertions.

I'm not familiar with this setup. But do you want for the server to boot as soon as it receive any packet addressed to its IP?

You need to send the WOL packet to the broadcast address of your network, not to the machine IP address. It this way all the machines on the network will receive it, including the ones that have been powered off for a while

I remember searching for a similar workaround in the past. I'm not sure parallel will work because the whole automation is blocked on error if I recall correctly. A workaround I found suggested on the ha website (but never tried) was to put the command that may error in a script and run the script as "fire and forget" from the automation. If the automation doesn't wait for the script to finish it won't detect the error either. But, as other pointed out, try to make the zigbee network more stable first.

Also, since zigbee is a mesh network, the fix could be as easy as adding a smart plug halfway between the controller and the light. Every zigbee device not running on battery works as a repeater too

Just use the directory listing of your favourite web server. You have a HTTP read only view of a directory and all of its content. If you self host likely you have already a reverse proxy, so it is just matter of updating its configuration. I'm sure it is supported by Apache, Nginx, LightHttpd, and Caddy. But I would expect every webserver supports it. Caddy is the easiest to use if you need to start from scratch.

I use filestash. I like it because it can connect with so many backends. In my setup it uses samba behind the scenes all the shares permissions are in a single configuration and I don't have to worry about a different set of user credentials.