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

help-circle
  • As others noted, the only way to improve CPU performance is either by making the CPU/RAM actually faster (higher clock speed, better/newer CPU, faster RAM so the CPU wastes less time waiting for the data read) or by wasting less of the CPU resources on useless/needless work. Caching helps in the later case, like waiting less time for reads that are cached in memory, or avoiding recomputing something you already computed before. However, Linux already has the page cache that uses free RAM to cache disk reads, and using more memory to cache computation results is a compromise that has to be decided by the software developers before it’s even shipped to you, so not much you can do there.



  • That’s why mixing OSs is a good way to spread the eggs in more baskets, so do consider using BSD. However, you are wrong on both claims, WireGuard is UDP only, it doesn’t use TCP, and my Alpine guest has had SSH disabled since the beginning, it can only be managed through the virtual serial port from the host OS, so locally only (unless someone manages to escape the VM), plus the SSH vulnerability was only possible when using OpenSSH, but one of the reasons for going with Alpine with musl was to avoid using the same packages as on my service hosts and use those that are smaller with less moving parts, so I’d have used Dropbear instead anyway.


  • Greg Kroah-Hartman (the 2nd person in command in Linux) recently had a public talk where he discussed the whole situation with vulnerabilities. There he predicted that this would calmn down for Linux eventually, since, due to it being open source, there was always attempts to uphold a certain level of code quality, so the number of issues are quickly reducing as they are being addressed. However, having spoken to some developers working on closed source projects, he revealed how terrified they all are with the current situation, since they never had this kind of pressure to keep good code, so the technical debt is crazy for them.


  • Yeah but you need to draw the line somewhere. With a VPN the attacker needs to compromise 2 different layers, which is far harder and less likely, especially if you put the VPN in a dedicated VM on a separate VLAN. If you are especially paranoid, you’d use a simpler VPN, like WireGuard, that has less chances of having unnoticed issues (code is small and well vetted), and use a different OS to run the VPN from the one running your services, so a critical flaw in one of the OSs is not enough for a full compromise.

    Personally, I run all my services in Debian/Ubuntu systems, but they are behind WireGuard running in Alpine Linux VMs, which use musl instead of glibc, though I’ve considered using BSD there.








  • 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