sunnamed434
commented
1 year ago Working since June of 2022 on BitMono, you can use this protector for Mono and whole .NET, but I'd recommend using that for Mono cuz most of the protections uses Mono vulnerabilities and this is why it's cool :D, this is not a fork of ConfuserEx, but, it's something new tbh, so I can't say that there are good protections atm, but doing pretty the architecture of the project and also preparing to the release, doing benchmarks and unit tests. As the result, BitMono is very easy to use and support because of the clean code and architecture, I agree that in some cases this is not the best, but trying to do this good, also I'm trying to look forward at other obfuscators/protectors even private to see their mistakes that they're done, for example, the features that users asking for they're very easy to implement and they're so useful and developers are just ignoring them even when there's PR for months with the feature implementation.. Anyone who is ready to upgrade your skills in RE or .NET or light up on some new project even just use it, you're welcome! 👍
Current BitMono TODOs
- As much as possible cross-platform.
- ControlFlow
- Unity (tool) plugin such as MSBuild -> build -> automatic obfuscation
- MSBuild plugin -> build -> automatic obfuscation
- MSBuild plugin + Azure/AWS support
- Improvement of the changelog (some examples: dnSpy, telegram, keepchangelog, holly-hacker dnspy plugin)
- Localizations
- Rewrite the BitMono.Host using .NET Generic Host such as in ASP.NET
- ~Reflection analysis~ (implemented in 0.8.0)
- Improve protections, code refactoring, etc
There are a lot more todos, but I think this is the main things
BitMono implemented CLI and GUI, I don't even pre-released the GUI yet cuz I probably made a big mistake by choosing a bad framework for that called MAUI Blazor, this is so buggy and unstable yet. I'm thinking about Avalonia.
Currently in BitMono implemented such features
- StringsEncryption (simple string encryption, I think this is so bad)
- BitDotNet (broken PE, working with PE32 and PE32+)
- BitMethodDotnet (broken methods)
- DotNetHook (hooks)
- Call to calli (this is not just like in ConfuserEx mod by bed and using the Ldftn and method signature, in BitMono its works differently, it calls member by its function pointer using its token)
- ObjectReturnType
- NoNamespaces
- FullRenamer
- AntiDebugBreakpoints
- AntiDecompiler (crashed dnSpy while analyzing the types)
- BitDateTimeStamp (I don't think you want to show when you compiled the file, just erase it)
- BitMono (fools the decompilers/unpackers/tools to make that there's no .NET metadata in PE file)
~Atm coming to the new protection called BitMono (working with PE32 and PE32+), which fools most of the tools and says that there's no .NET PE Metadata~ (implemented in 0.8.0 version)
How you can support the project
- Press star
- Contribute
- Write issues
- Share the project
- Use BitMono
Remarks
- BitMono structure very-very similar to Confuser, but with clean code, also most of the things in BitMono works simpler and with less code
- BitMono uses AsmResolver instead of dnlib, and this is very important to know, but, AsmResolver is practically no different from dnlib, the same as with Confuser and BitMono
- In past BitMono used dnlib but migrated to AsmResolver, here's why
LaraSQP
tshcherban
It is time we start compiling a list of alternatives to this project, from viable forks to... well, anything.
Let us use this thread as a repository of options.