StarDreamer

Simply changing the binary worked for me. Been more than 1 month and no migration issues.

It does still show gitea branding, however.

Also if the router blocks icmp for some reason you can always manually send an ARP request and check the response latency.

Is there a specific reason you’re looking at shadowsocks? The original developer has been MIA for years. People who used it in the past largely consider it insecure for its original stated purpose

trojan-gfw is a better modern replacement. However that requires a certificate in order to work. You can easily get one via lets encrypt.

At this point, let Shadowsocks, obfs, and kcp die a graceful death like GoAgent before it did.

Another thing you can look into is apptainer/singularity. Basically portable container binaries. Executing the binary automatically runs a program/drops you into a shell inside the container with your $HOME mounted inside. Stuff like cuda also work as long as your host system has appropriate drivers.

You can also port docker containers to apptainer directly via cli.

Oh wow. It supports Kobos as well. Gonna have to check this out. Thanks.

Just in time to move to IPv6!

What someone does with their 16,777,215 private IPv4 addresses is none of our business…

Now just connect all of that with dumb L2 switches and watch those broadcasts fly!

No, the 2037 problem is fixing the Y2k38 problem in 2037.

Before that there’s no problem :)

Can’t comment much about the docker side since it’s not something I’m familiar with.

For the kernel part, assuming what you’re referring to as UUIDs is the pid namespace mechanism, I’m failing to see how that would add overhead with containers. The namespace lookups/permission checks are performed regardless of whether the process is in a container or not. There is no fast path for non-containerized processes. The worst overhead that this could add is probably one extra ptr chase in the namespace linked list.

CrowdSec has completely replaced fail2ban for me. It’s a bit harder to setup but it’s way more flexible with bans/statistics/etc. Also uses less ram.

It’s also fun to watch the ban counter go up for things that I would never think about configuring on fail2ban, such as nginx CVEs.

Edit: fixed url. Oops!