Cyber.
@donb
- 232 Followers
- 80 Following
- 225 Posts
Truth takes time.
I wrote a TCP/IPv4 network stack sniffing/mangling library in Python3. It overloads python dicts to work, which makes parsing and editing packets very elegant. Check it out here, it's GPL'd:
https://github.com/securitymouse/moops-public
https://github.com/securitymouse/moops-public
@cynicalsecurity a stateless computing environment is pretty much what I'm working on at Lab Mouse and tbh 1) I had never heard of Olivette and 2) I didn't know Johanna ever released a paper on stateless systems. hehe
Introducing http://careful.is the 1st Open Source Healthcare think-tank intending to build ideas toward free & open insurance program.
Introducing http://careful.is the 1st Open Source Healthcare think-tank intending to build ideas toward a free & open insurance program.
@egypt @HalvarFlake @kwanre @saper yes in that context I fully agree with you. I've written a lot of Linux kernel bugs before I understood anything about the Linux kernel.
I'm talking here about systemic issues that are harder to find unless you understand the relationships between technologies and their security models.
@HalvarFlake @kwanre @saper did you read my recent blog post on the RISC-V MCM flaws?
A point I made in that piece is that exploit engineering (in the context of complex exploit dev) requires a thousand-foot view of an entire technology to succeed, while engineers are often cordoned off to specific subsets of technologies.
Complementary skills, but very different perspectives.
@saper @HalvarFlake @kwanre I think that absolutely used to be true. It used to blow people's minds to put more than system() shellcode in a payload. Today, I think the best exploit developers are also engineers because they have to be.
On Princeton's discovery of security-impacting flaws in #RISC-V MCM: Don't rely on Linus' Law to secure CPU architectures!
http://blog.securitymouse.com/2017/04/the-risc-v-files-princeton-mcm-and.html
@HalvarFlake @kwanre in the past few years I decided to go back and re-write my exploits once they are "good enough" because I want them to be more clean/accurate/readable, not just for others, but for myself.
I'll never forget the emails from a leaked email spool around ~2002 when the US Army said one of jduck's exploits was "the cleanest we had ever seen". And it was. ;-)