Just two days left until the first hearing in Newag's lawsuit against us (Dragon Sector members) and SPS. It will take place on 28.08.2024 at 10:00. In case you've missed it, we're being accused of infringing upon Newag's intellectual property and unfair competition. This is, of course, bullshit and a great example of a SLAPP case.
I get really annoyed when a link unexpectedly takes me to X, but since I ended up there today, this is too good not to share.
AI literally Rickrolled a company's customer when they asked for a link to a training video! It replied to a request by sending a link to Rick Astley's video on YouTube.
We're 7 years after the publication of NIST 800-63 on best practice guidance for modern passwords and I still talk to large companies stuck in the past trying to enforce silly password rules and mandatory 90 day rotations. Pretty sure I'm still going to be having these discussions at the 10 year anniversary.
Google's removal of the estimated number of search results is particularly user-hostile.
And it's me. I'm "user".
There's a specific kind of searching where you know that there shouldn't be a ton of results, and you are adding exclusions until your search matches the expected result space.
And now that's impossible (without scrolling to the bottom to see how many pages of results there are).
Some thoughts on memory safety
https://pacibsp.github.io/2024/some-thoughts-on-memory-safety.html
This post briefly describes some theoretical aspects of memory safety that feel important to me but that aren't always obvious from how I see memory safety being discussed:
1. Memory unsafety is a specific instance of a more general pattern of handle/object unsafety
2. Memory unsafety is relative to a particular layer in a stack of abstract machines
3. Memory unsafety matters because it violates local reasoning about state
4. Safe languages use invariants to provide memory safety, but these invariants do not define memory safety
Also, not sure what was up with the embed in my last post, hopefully this one works.
Another SolarWinds RCE vulnerability…
… I instantly had the image from Hunt for Red October when the Soviet ambassador tells the US SecState that they needed help and SecState says "Don't tell me you lost _another_ submarine!"
I have some words for the developers who decided that it was completely reasonable to expect a user to be able to precisely hit a single pixel to be able to resize a window.
I've seen this on both Windows and Linux. 🤦♂️
GNU/Linux Sandboxing - A Brief Review https://hardenedlinux.org/blog/2024-08-20-gnu/linux-sandboxing-a-brief-review/
Most mirrors of libgen are now down. Anna's Archive is fighting to keep the lights on.
https://annas-archive.org/
Last year on this day the bogus #curl CVE arrived that triggered a series of events that subsequently made #curl become a CNA.
https://daniel.haxx.se/blog/2023/08/26/cve-2020-19909-is-everything-that-is-wrong-with-cves/
Brief intro on how to use eBPF for syscalls tracing
Andy Jassy talks about the benefits Amazon is seeing from their AI coding assistant. It’s widespread that devs are more productive with these tools.
The question is whether this is like accountants and Excel where it creates jobs or travel agents & the web where it kills them.
PageJack: A Powerful Exploit Technique With Page-Level UAF
A talk by @pkqzy888 et al. about overwriting slab objects containing a `struct page *` field to achieve arbitrary read/write in physical memory.
So I made a thing ☺️
Converted #phnt (Native API header files from the System Informer project) to #IDA TIL, IDC.
To import "phnt" types and function definitions to IDA and help with Reverse Engineering.
@hexrayssa @mrexodia
Introducing #IDA_PHNT_TYPES:
https://github.com/Dump-GUY/IDA_PHNT_TYPES
Being a C programmer in 2024 is so ridiculous, look what I need to do! Every (!) evening I have to charge my sacrifice cats, complete the ritual and pray to the gods just to be as memory safes as Ru^\x00
Programm terminated with signal SIGSEGV, Segmentation fault