Loic Nageleisen retweeted
Link: Kharkiv Rubyist during the war: We are still here
zverok.space/blog/2022-03-15…
Loic Nageleisen retweeted
Correction: the thing they were critiquing (order of backtrace printing) was changed in 2.5.0, which was released four years ago. Still, four years is a while ago and you should keep tabs on other languages if you are a generalized programming expert.
bigbinary.com/blog/ruby-2-5-…
Loic Nageleisen retweeted
It makes me caremad that so many programming experts on Twitch/Discord/etc love to critique Ruby, but will reference 1.8/1.9 issues, but were fixed back in 2.0.0 which was released _nine_ years ago. Technology changes, and so should your critiques.
Loic Nageleisen retweeted
Picard career tip: The grass may seem greener on the other side, but sometimes it's because of all the fertilizer.
Loic Nageleisen retweeted
I love this idea from @icculus - pool resources to issue micro-grants to open source projects: icculus.org/microgrant/news/…
Loic Nageleisen retweeted
Picard management tip: Don't negotiate absurd schedules with engineers. Encourage truth telling and reasonable time estimates.
Loic Nageleisen retweeted
Stop building position independent code
Libraries are not meant to be shared
Years of ASLR yet no hackers blocked by moving shit around
Wanna load a DLL in the wrong address for a laugh? COFF had a table for that: it's called "relocations"
They have played us for relative fools
Loic Nageleisen retweeted
Sometimes you read an essay that's about more than what it's about, and this one, about the motivations underlying free and open source software development, is a really good example.
apenwarr.ca/log/20211229?s=0…
Loic Nageleisen retweeted
Someone (@_ianks) finally managed to integrate Rust into rubygems archaic C extensions build system! Maybe this will open the door for Zig based extensions as well? #ruby #rust
github.com/rubygems/rubygems…
Loic Nageleisen retweeted
Having a shell script build up a giant regex is pretty clever and portable. Dude is really close to building a PEG parser generator with shell script. PS: if you can, please just write a parser using your favorite parser library.
Probably the most comprehensive Regex I’ve seen yet to identify Log4Shell exploitation attempts:
github.com/back2root/log4she…
#CVE-2021-44228 #Log4j
Loic Nageleisen retweeted
This thread is pure beauty. How did I miss this thread before?
Replying to @moxie
Update: my NFT was removed by OpenSea without warning or explanation. I don’t see any terms it violated?
No problem, this is web3 right? But the NFT also disappeared from my crypto wallet! Why? Because MetaMask just calls the OpenSea API. Loving the decentralized future so far..
Loic Nageleisen retweeted
This exploit is not the usual “we overwrote some memory”. They abuse a file format description to create a virtual machine out of a handful of logical operators to compute addresses at runtime and required its own compiler. This is wild.
Today we're publishing a detailed technical writeup of FORCEDENTRY, the zero-click iMessage exploit linked by Citizen Lab to the exploitation of journalists,
activists and dissidents around the world. googleprojectzero.blogspot.c…
Loic Nageleisen retweeted
the most important thing about the log4j incident is that it’s clear and incontrovertible evidence in support of whatever beliefs i already have about software development
Loic Nageleisen retweeted
the #log4j scramble in a nutshell – at North-East Region, Singapore
Loic Nageleisen retweeted
after that i wrote a program that queried for existing 1-bit-offset packages and then statically analyzed them for suspicious patterns (like importing the original non-corrupted package name). i found several malicious things doing god knows what and reported them
Loic Nageleisen retweeted
1970: We're going to build a global network that can withstand a nuclear war.
2021: AWS is down and my coffee machine doesn't work.




















