infosex.exchange <3

You are probably looking for the infosec.exchange Mastodon instance

This host is mostly for my random stuff, and in little part acts like a well-intentioned placeholder for the typosquatted domain.

Discoverability and Archiving

Currently I'm using this host for saving the items from my own feeds to the Wayback Machine and provide in-links for search engines. I hate that I have to do this, but the non-sense ideology of Mastodon pretty much ruined the search feature for Fediverse as a whole, and this wasn't changed by the fact that they owned their mistake and implemented search eventually.

Yes, I (or anyone else) could do similar things with other peoples published feeds, regardless of the tantrum. No, you can't defederate this, because the process doesn't rely on an instance.

Gluttony Section for Search Engines

[RSS] Reverse engineering the Creative Katana V2X soundbar to be able to control it from Linux

https://blog.nns.ee/2026/02/20/katana-v2x-re/
this post | permalink
[RSS] Discovery & Analysis of CVE-2025-29969

https://www.safebreach.com/blog/safebreach_labs_discovers_cve-2025-29969/

(Windows MS-EVEN RPC Remote Code Execution Vulnerability)
this post | permalink
[RSS] Mailbag: URLs as UI

https://unsung.aresluna.org/mailbag-urls-as-ui
this post | permalink
[RSS] OpenCFD OpenFOAM Code Stream directive arbitrary code execution vulnerability

https://talosintelligence.com/vulnerability_reports/TALOS-2025-2292
this post | permalink
@leyrer Wait till one of those techbros announce they reserved capacity for future weapons manufacturing...
this post | permalink
[RSS] CVE-2026-20841: Arbitrary Code Execution in the Windows Notepad

https://www.thezdi.com/blog/2026/2/19/cve-2026-20841-arbitrary-code-execution-in-the-windows-notepad

ZDI analysis of the notorious vuln
this post | permalink
[RSS] "Good enough" emulation: Fuzzing a single thread to uncover vulnerabilities

https://blog.talosintelligence.com/good-enough-emulation/
this post | permalink
Paged Out zine #8

https://pagedout.institute/download/PagedOut_008.pdf
this post | permalink
So the apparent concurrency bug I've been chasing for the last couple of days turned out to be:

- a thread panic!ing
- because it couldn't allocate a trivial amount of memory
- probably related to the fact that when I passed a struct to a library, the library apparently decided that the passed fields are not important and made up new ones

The best part was that I saw no indication of the panic until I carefully yanked out half of the code (using a different library), some of which apparently swallowed all panics.

Yes, I work with weird shit.

#Rust
this post | permalink
[RSS] Carelessness versus craftsmanship in cryptography

https://blog.trailofbits.com/2026/02/18/carelessness-versus-craftsmanship-in-cryptography/
this post | permalink
Next Page