This feels like it has validated my decision to just use plain wireguard and hardcode my client list. It’s really not too hard to set up, barely different that configuring authorized_keys or ssh.
Check out my open source game engine! https://strayphotons.net/ https://git.sw0.com/frustra/strayphotons
I have been developing this engine on and off for over 10 years, and still have big plans.
- 0 Posts
- 5 Comments
I guess someone stole the 1 and 3 off the sign in OPs picture, they’re there on street view. That’s wild you found this
That would be the AI denoising that basically every phone runs automatically, and pretty much the entire reason I bought a standalone camera…
xthexder@l.sw0.comto
Selfhosted@lemmy.world•There isn't an easy exploit for this PHP vulnerabilityEnglish
7·7 days agoWhat confuses me as someone who hasn’t written PHP in ages, is why is it supposedly so easy for a request to hit the memory limit? Does this only work on servers that accept user uploads and other large request payloads? People are saying a static PHP page can be exploited, but I don’t understand how if it’s behind even a basic nginx instance with default request limit of 1MB.


This seems like a decent guide on how to set it up:
https://www.cyberciti.biz/faq/how-to-set-up-wireguard-firewall-rules-in-linux/
It’s very similar to the config I’ve got. The nat iptables stuff in step 1 is what enables wireguard to be used as a VPN exit node. (+ net.ipv4.ip_forward=1)