

AllowedIPs is a client side restriction that can be ignored anyway, no real security benefit from not just putting your entire network there.


AllowedIPs is a client side restriction that can be ignored anyway, no real security benefit from not just putting your entire network there.


You can just specify AllowedIPs in the wireguard client config to route only traffic to your services through the VPN, works great.


And does this date field force you to enter your real DOB?


All the other software is not the init system, FFS.


Snap is Canonical’s project AFAIK
He probably means Ubiquiti network gear


Yes, but it is a binary blob that Google makes and Firefox just integrates with. If it is not released for a specific platform, Firefox can’t do anything about it. At least a while a go it was quite an adventure to try and get DRM working on ARM64 Linux: https://www.da.vidbuchanan.co.uk/blog/netflix-on-asahi.html


This is good even if you don’t care about Chrome, because it means Widevine should become properly supported on the platform.
Oh yeah, installing Steam from a flatpak also seems to be a good way to avoid some tinkering, I don’t think they have ever done that.


Like hard reset required “bricked” or dumpster bricked?


Android TV also had similar issues


I wouldn’t expect it to matter much, idle processes are pretty cheap.
…in a virtual machine


Doesn’t LTS change like twice a year nowadays?
Are you sure that’s not a monitor setting?


Does that laptop have an SSD?


FreeBSD is closer to Unix than Linux is
Question is how “real” that support is - firmware updates matter and depend mostly on the chip manufacturer’s support.
Since the issue is only on the ssh server side, it does not even matter if it is installed, because it would not normally be running. Ssh’ing to containers does not seem like a common practice at all.