There's something very special about this specific gigachad gif. His facial expressions are so extremely human and relatably funny to me, and for some reason reminiscent of Mediterranean people
There hasn't been a single time I've looked at this gif and not laughed out loud
@dcolascione Need to go back in time and make sure current x86 has half the available registers and demonstrate that hardcoding addresses speeds up php interpretation by a whole quarter percentage in specific cases
@julianor nodejs linux official builds are no-pie by default for perf reasons. some distributions like debian/alpine rebuild node, which can enable pie
here's a tracking issue for it: https://t.co/7mfiw2OGuh
@tmuxvim Ignoring that Tailscale trusts the coordinator on the list of all nodes that have access to the tailnet by default, and tailnet lock being opt in, are you retarded?
@dcolascione I've read some of its code and it does a bit too much too... way too many syscalls for a simple C program, but I guess it does it right, just a bit scary
@dcolascione Not DANE, but close enough, and if you trust the dnssec chain you can trust it fine. Unfortunate that that config key is false by default though
@dcolascione Did not know this. This is an extremely good idea, I shall implement this in my own setup. Also reject non-PIE static binaries at the kernel level.
PIE is position-independent addressing for your machine codeslop. Basically just using offsets from current location, so you can place the machine code wherever (ASLR = address space layout randomization, basically scatter out your code into random addresses, so attackers can't hard code addrs while overwriting memory) & not be pwned immediately in case of memory unsafety (like a pointer overrun that overwrites data etc)
How important is it? Extremely. https://t.co/YkFd5W8sm0
We have known for FUCKING DECADES about the need to randomize address spaces so that memory corruption failures in unsafe native code don't become exploits. With ASLR, to use an exploit, you need to not only have a memory bug, but win a 1/2^24 lottery. (Yes, info leaks exist, but they require separate bugs.)
By turning off ASLR, these selfish pricks against the human race reduced exploit difficulty from 1/2^24 to 1/1. These are the people who would leave a space station airlock open if they felt warm. At least Chernobyl had radiation shielding. These people wouldn't even build it. You can't have a society if there are no consequences for reckless endangerment of the public. You can't just enjoy private, immediate benchmark wins and socialize the losses later when your non-PIE shit run by naive innocent bystanders is compromised because you refused the most basic of automated risk reduction measures.
Shame on these people.
These people should be shot into the sun. For trivial perf win, they turned off one of the few ways to mitigate bugs in unsafe code. These pathetic slugs, these reckless, retarded, shit for brain morons have endangered the whole internet for nothing. Fuck them with a broom.
These people should be shot into the sun. For trivial perf win, they turned off one of the few ways to mitigate bugs in unsafe code. These pathetic slugs, these reckless, retarded, shit for brain morons have endangered the whole internet for nothing. Fuck them with a broom.
@MostlyMonkey Easiest way to lose the desire to be rich is to be exposed to it all the time
It really changes nothing. Not meaningfully different from earning low 6figs in most parts of the world. Money won't fill the hole in your heart. Have kids