Matthew Seyer

152 Followers
99 Following
57 Posts
I started using the #rustlang clap library back when it was version 2. I somehow missed when it went to 3. I come back to it on 4 and it has changed so much I'm having to relearn it. At first it irritated me because none of my old templates that I'm so accustomed to copy/pasting into all my projects no longer works... but now as I start learning the new version, I am really liking it. Being able to define my application as a struct and then implement functionality for it has advantages.
Venison chili queso empanadas!
https://github.com/pozm/bsod-rs
“The safest library on the block. Calling the bsod function will cause a blue screen of death.”
I love looking at the source code for stuff like this!! I always learn new ways of doing things.
This is a good example on how you can use LoadLibraryA.
#rustlang #dfir
GitHub - pozm/bsod-rs: The safest library on the block. Calling the bsod function will cause a blue screen of death.

The safest library on the block. Calling the bsod function will cause a blue screen of death. - GitHub - pozm/bsod-rs: The safest library on the block. Calling the bsod function will cause a blue s...

GitHub
I’m still on the bus… so let me tell you about my biggest #rustlang failure starting out!!
When I first started I thought I had to approach Rust like C. Also, I didn’t know C, so that was dumb anyways. I thought in C you just mem copy a buffer into a structure. So I tried doing that with Rust. It worked kind of for this example, but quickly led to so many issues as my structures got slightly more complex… Needless to say, every tool has its function, but this was not the right tool for the job.