• 0 Posts
  • 25 Comments
Joined 2 months ago
cake
Cake day: October 3rd, 2026

help-circle



  • Firstly, not legal advice here, I’m not a lawyer.

    A license is just a set of terms that dictate what you can and cannot do, so you can write whatever you want there (though I’d advise the help of a lawyer if you do so). However , only those licenses that satisfy certain requirements can officially be called and considered Open Source_, among which, one of the most important ones is that you cannot control how and for what the downstream users use the code, so a if you use a true open source license, you can prohibit someone from forking, adding ads and such to it and distributing wherever they want. If you want such clause, your license can’t be “open source”, but if you are fine with that, it’s your choice, so do whatever you want.

    PS. Note that the license is only important as long as it is actually enforced, so doesn’t matter what it says if everyone ignores it. For example, uBlock Origin is licensed under GPLv3, so any derivative should provide the modified source code to the users, but most commercial ad blocking browser extensions are based on it and violate this clause, but the uBlock creators stopped caring about it since the legal headaches are not worth it.








  • I actually did that. Or well, I was planning to upgrade the Debian version and instead of doing it in place I replaced the drive (kept the old around for a while just in case) and did a clean install. I didn’t make any new backups or moved configs or anything outside what I already had, the system was back to operations faily quickly. The main reason, I have a markdown file describing every configuration and recovery step needed to get a fresh system to a fully working state in case of a disaster, and my test showed that it worked great. It does take a bit of effort to keep it up-to-date, but as shown, really worth it, and it douples as a small wiki for accumulated knowledge. I do wish to play with Ansible at some point if I have the time, but this works for now.





    • Forgejo for private git repos, coz F GitHub (F as in paying respect obviously… :v)
    • Portainer, though don’t use much as of late as I got used to the CLI
    • qBittorrent for Linux ISOs. No, really, I use it to download Linux ISOs :v
    • WireGuard, several instances, some for accessing specific services, one for accessing GeoIP blocked content when traveling
    • Vaultwarden for managing passwords
    • Home Assistant for managing a couple of sensors
    • Nginx Proxy Manager for managing hosts
    • TeamSpeak 6, just playing around with the beta for now
    • Apache Subversion for private SVN repos
    • A handmade C# service for storing some MQTT data into a database
    • peaNUT a NUT dashboard for the UPS
    • RustDesk for remote management of desktops

    As for the hardware:

    • A Raspberry pi 4 running Docker containers
    • A Dell Wyse 5070 (16GB) running Proxmox with mainly Alpine Linux VMs




  • You could spin a publicly exposed WireGuard daemon firewalled to allow peers access to the non-public SSH port only, which would result in double encryption, but would give you the peace of mind that an attacker would have to compromise both at the same time, which is very unlikely. Plus, WireGuard is very cheap to deploy and produces no logs. We use that model in my office to access our server.

    Edit: Otherwise, as others mentioned, you’d move the SSH daemon to a random port, disable password login and weaker keys and cyphers, setup Fail2ban, and optionally setup GeoIP blocking (only allow IPs from your region to connect).