RE: https://infosec.exchange/@da_667/115571074603961987
*Matthew Prince watching the Polymarket bets on which higher paying odds option they will stake and write their Root Cause doc to align with*
RE: https://infosec.exchange/@da_667/115571074603961987
*Matthew Prince watching the Polymarket bets on which higher paying odds option they will stake and write their Root Cause doc to align with*
Try this one weird trick to reduce entropy and forestall the heat death of the universe:
cat /dev/random > /dev/null
A lot of work is already being done on backdoor analysis for CVE-2024-3094 (the xz/liblzma backdoor). I started some high-level analysis of code work for the actors on the reposity at tukaani.org in an attempt to better understand possible motives or other areas of the codebase they may have been targeting for abuse.
tl;dr; a lot of the commits seem legitimate (at least on the surface), but there were some interesting choices along the way. #xz #xzbackdoor
I suppose I'll do a small #introduction
(edit:Update for 2025)
I am a #cybersecurity engineer (ex-AWS), and have spent much of the last decade in the enterprise space. My primary focus was network, endpoint, (and over the last 5 years) hybrid/public clouds. But of course in enterprise you're never just one thing. I've dabbled in everything across the security spectrum -- I really enjoy security #automation.
I also like #coding (Python, Golang, JS, C, whatever), #HTB, and building+breaking shit in my free time.