Over the past couple years, I have come to know the #dotnet platform pretty well, from a developer's and a #reversing standpoint.

I can’t always say the same the #infosec community.

Today, I decided to rant a little (or maybe a lot πŸ™ƒ)

πŸ‘‰ https://blog.washi.dev/posts/misconceptions-about-dotnet/

@washi

β€œI partially blame the #100DaysOfYara trend. I understand the idea is to have people write many YARA rules for practice. However, the amount of garbage that enters our community because of it is astounding.”

@washi great article! I'm particularly interested in obfuscation. Unfortunately, I take a dependency on a library that uses reflection and P/Invoke so trimming doesn't work. The app is delivered via Docker container so I thought I could use Ready To Run in the docker build but that fails with arithmetic overflow. Do you think if trimming doesn't work that it also rules out obfuscation?
@dmetzgar obfuscators have existed long before trimming and readytorun were introduced, so should work. You just may have to tell your obfuscator not to rename certain objects in your app if you rely on reflection finding these objects by name (usually through configuration or obfuscator sdk attributes).