

It’s not wrong that free RAM is wasted RAM, at least not if properly used for caching in a way that is simple and fast to release when the system does need more RAM.


It’s not wrong that free RAM is wasted RAM, at least not if properly used for caching in a way that is simple and fast to release when the system does need more RAM.
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.


Having its own data connection would just drain the battery faster. In theory, a Pebble has an open SDK, even the firmware is open, so you could hack whatever you want into it (as long as the resources suffice)
Put everything behind VPNs and migrate services from Docker to VMs


How is crashing on an unhandled path in a security context not better?!


I’ve also seen some sites use POWBlock, though, don’t know anything about it.


WireGuard is stateless, so running it “on” 24/7 is cheap, set it up once for them and leave it on, ideally they wouldn’t notice a thing.
Proxmox VM snapshots and backups, plus proxsave I assume?
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.


Huh?!


Wouldn’t be surprised if the big guys got first dibs before everyone else


Synology had a critical system and PHP package update yesterday, could it be related 🤔


I mean, unattended upgrades has it’s own config file where you can specify when to schedule a reboot (when needed), which you’d usually do in off-hours like 2 AM your local time, so changing the Systemd unit activation time seems like the wrong fix.
Edit: Nevermind, your issue was that the daemons were being rebooted, not the whole system, if I understood that correctly


As for the hardware:
For frequently changing data hourly up to 24, daily up to 7, weekly upto 4, monthly up to 12.
For daily changing data daily up to 7 and etc. as above.
For seldom changing data a backup every 3 days with rotation based on a storage quota, and retention of manually held samples.


Did you read it to the end?


Without root user login, the attacker would have to guess not only the password to the user but also the username (hopefully it’s not something simple like admin), and once you are logged in you can use sudo -i to chage into root, which will require a password, therefore, we also disable password login so if someone does manage to somehow compromise the SSH user, they’d still need the password to become root.
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.