115 Followers
22 Following
30 Posts

@cxiao yes, this indeed is the main point. It's almost artificially limiting yourself.

Though in fairness, I do think we as developers can also do better making our libraries more available to other ecosystems. Python is here to stay, whether we like it or not. Maybe these libraries just need a pypi package that people can just pip install.

@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).

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鈥檛 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/

Better late than never, I finally managed to finalize my #flareon12 write-ups馃槃

Overall, it was a fun set of challenges and the latter ones a reminder of how much I still have to learn in the field of RE :).

馃憠 https://blog.washi.dev/posts/flareon12/
馃憠 https://washi1337.github.io/ctf-writeups/writeups/flare-on/2025/
Image

#AsmResolver 6.0.0-beta.4 released!

This release addresses many shortcomings found during beta.3, including ARM32 and ARM64 support, auto references importing, and many other DX improvements.

馃憠 Get it on GitHub or NuGet: https://github.com/Washi1337/AsmResolver/releases/tag/v6.0.0-beta.4

#dotnet #pe #reversing

Release 6.0.0-beta.4 路 Washi1337/AsmResolver

It's been a while since the last beta.3 release, and the main reason for this has been that beta.3 saw many more testers actively trying out v6.0.0 and pushing it to its limits. Beta.4 addresses ma...

GitHub

After #flareon11 challenge 7, I got inspired to build tooling for #dotnet Native AOT reverse engineering.

As such, I built a #Ghidra Analyzer that can automatically recover most .NET types, methods and frozen objects (e.g., strings).

馃憠https://blog.washi.dev/posts/recovering-nativeaot-metadata/

Recovering Metadata from .NET Native AOT Binaries

Ever seen a binary that looks like a .NET binary based on its strings, but .NET decompilers are not able to open them?

Washi

#AsmResolver 6.0.0-beta.3 just got pushed to NuGet!

More bugs were found and squashed. We are closing in on a full release with most of the public API being stable.

Get it on GitHub or NuGet 馃憠 https://github.com/Washi1337/AsmResolver/releases/tag/v6.0.0-beta.3

#dotnet #pe #reversing

Release 6.0.0-beta.3 路 Washi1337/AsmResolver

This is a maintenance release. AsmResolver is closing in on a main release with most of the public API being stable. However, similar to 6.0.0-beta.2, this is still a pre-release and some of the pu...

GitHub

#AsmResolver 6.0.0-beta.2 has been released

This is a maintenance release that addresses many regressions introduced by the refactors in 6.0.0-beta.1.

Get it on NuGet or GitHub
馃憠 https://github.com/Washi1337/AsmResolver/releases/tag/v6.0.0-beta.2

Release 6.0.0-beta.2 路 Washi1337/AsmResolver

This is a maintenance release that fixes some shortcomings and addresses various regressions introduced by the refactors in 6.0.0-beta.1. Similar to 6.0.0-beta.1, this is an unstable release and th...

GitHub

I just published my writeups for all challenges of #flareon11:

馃憠 https://blog.washi.dev/posts/flareon11/

馃憠 https://washi1337.github.io/ctf-writeups/writeups/flare-on/2024/

Hope you like them as much as I liked writing them!

Flare-On 11 Write-Ups

Today a short post.

Washi
CrowdStrike Global:Offensive