after reading up how to secure the VPS, I added ufw rules to drop all incoming traffic except SSH and syncthing, disabled root SSH access, created a dedicated user for syncthing, switched on unattended upgrades.
what other measures should I take to harden #linux and #syncthing ?
@kaia If the VPS has some kind of virtual console access (VNC, noVNC or similar), make sure it's turned off once you have everything set up and only ever turn it on for emergency maintenance.
@kaia It may be trivial, or maybe I'm overthinking of things, but make sure you have some good resource how to set things up.
In case if you want to duplicate the setup or something goes wrong in the future you have a handy resource.
I personally use some ansible script for the basic setup. But some shell script or Readme.md file could be just as good. Even taking notes like follow this guide, plus setup this and this can be helpful.
@lain@kaia Since we don't usually handle floppy disks by the shutter end, we'd have to pick them up by the shutter the way they're in the box.
There's lots of controversy about whether the labels go in one orientation or the other, depending on whether you care that they're readable when you're about to insert them versus when they're in their storage box, but that's another matter.
@kaia 1: ubuntu isn't recommended if you want hardened security as it already ships proprietary blobs. 2: Separate partitions and do proper mounting options
@kaia In theory it's possible. When I lived in paris, I followed a friend of mine messing up with such issue. And he basically was able to replace the whole system with Gentoo by chrooting himself. The other objective of that was to also have the VPS host no data, and only pull data from the house SBC he had and treat the request on the vps (basically via a network file system).