Explore >> Select a destination
|
You are here 
|
parsiya.net | ||
| | | | |
sensepost.com
|
|
| | | | | Leaders in Information Security | |
| | | | |
blog.quarkslab.com
|
|
| | | | | Following our presentation at Black Hat USA, in this blog post we provide some details on CVE-2022-20233, the latest vulnerability we found on Titan M, and how we exploited it to obtain code execution on the chip. | |
| | | | |
soatok.blog
|
|
| | | | | Just to assuage any panic, let me state this up front. If you're reading this blog post wondering if your Lobste.rs account is at risk, good news: I didn't publish it until after the vulnerability was mitigated, so you're safe. You don't need to change your passwords or anything. This write-up is purely for education... | |
| | | | |
jmmv.dev
|
|
| | | In a recent work discussion, I came across an argument that didn't sound quite right. The claim was that we needed to set up containers in our developer machines in order to run tests against a modern glibc. The justifications were that using LD_LIBRARY_PATH to load a different glibc didn't work and statically linking glibc wasn't possible either. But... running a program against a version of glibc that's different from the one installed on the system seems like a pretty standard requirement, doesn't it?... | ||
