Merge pull request #131 from sunnamed434/dev

Bump new version 0.16.1

Author: sunnamed434

BitMono.sln

@@ -12,6 +12,7 @@ Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Solution Items", "Solution
 		LICENSE = LICENSE
 		README.md = README.md
 		props\SharedProjectProps.props = props\SharedProjectProps.props
+		props\SharedPackages.props = props\SharedPackages.props
 	EndProjectSection
 EndProject
 Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "src", "src", "{D87066C4-1144-4BD8-96E9-9F4676001397}"

BitMono.sln.DotSettings

@@ -1,6 +1,8 @@
 <wpf:ResourceDictionary xml:space="preserve" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:s="clr-namespace:System;assembly=mscorlib" xmlns:ss="urn:shemas-jetbrains-com:settings-storage-xaml" xmlns:wpf="http://schemas.microsoft.com/winfx/2006/xaml/presentation">
 	<s:Boolean x:Key="/Default/CodeEditing/SuppressUninitializedWarningFix/Enabled/@EntryValue">False</s:Boolean>
+	<s:String x:Key="/Default/CodeStyle/Naming/CSharpNaming/Abbreviations/=ASCII/@EntryIndexedValue">ASCII</s:String>
 	<s:String x:Key="/Default/CodeStyle/Naming/CSharpNaming/Abbreviations/=CLI/@EntryIndexedValue">CLI</s:String>
 	<s:String x:Key="/Default/CodeStyle/Naming/CSharpNaming/Abbreviations/=JS/@EntryIndexedValue">JS</s:String>
 	<s:String x:Key="/Default/CodeStyle/Naming/CSharpNaming/Abbreviations/=NET/@EntryIndexedValue">NET</s:String>
+	<s:Boolean x:Key="/Default/UserDictionary/Words/=Decryptor/@EntryIndexedValue">True</s:Boolean>
 	<s:Boolean x:Key="/Default/UserDictionary/Words/=Ldasm/@EntryIndexedValue">True</s:Boolean></wpf:ResourceDictionary>

CHANGELOG.md

@@ -7,6 +7,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 | Versions:                     |
 |-------------------------------|
+| [0.16.1-alpha](#0161-alpha30) |
 | [0.16.0-alpha](#0160-alpha29) |
 | [0.15.1-alpha](#0151-alpha28) |
 | [0.15.0-alpha](#0150-alpha27) |
@@ -27,6 +28,23 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ---
 
+## 0.16.1-alpha.30
+2023-07-17
+
+### Added
+
+- New docs.
+
+### Fixed
+
+- (UnmanagedString) Add unicode support, fix strings with null characters [#130](https://github.com/sunnamed434/BitMono/pull/130), thanks [GazziFX](https://github.com/GazziFX)
+- Other minor bug fixes.
+
+### Changed
+
+- Bumped to the latest AsmResolver 5.4.0 version.
+- Code refactoring and possible bug fixes.
+
 ## 0.16.0-alpha.29
 2023-05-14
 

README.md

@@ -58,11 +58,11 @@ So, if you will add more protection to the file, I think it would seem like tota
 Read the **[docs][bitmono_docs]** to read protection, functionality, and more.
 
 ## How your app will look since BitMono obfuscation - just in a few words
-* Looks like C++ application but is an actual C# application
-* Crash of decompilers when analyzing types
-* Broken decompilers
-* Broken IL Code
-* Invisible types
+* Looks like C++ application but is an actual C# application;
+* Crash of decompilers when analyzing types;
+* Broken decompilers;
+* Broken IL Code;
+* Invisible types;
 * No code
 
 ## Features

docs/bestpractices/zero-risk-obfuscation.rst

@@ -0,0 +1,81 @@
+Zero Risk of Obfuscation
+========================
+
+You may have a project which is really heavy and you don't want to loose any perfomance of it, so, well, you can't really have zero losses of perfomance but you can minimize it, due to BitMono is not really stable with all runtimes and this is very complex obfuscation, would really recommend to use this, as we call it `BitMono Starter Pack for Mono` - like in Fortnite :D
+ 
+1. AntiDecompiler
+2. BitMethodDotnet
+3. BitTimeDateStamp
+4. BitDotNet
+5. BitMono
+6. (Not optional) StringsEncryption, if you really-really need to encrypt strings, this may very-very-very harmful to the application's performance
+
+
+`protections.json` will look like this:
+
+.. code-block:: json
+
+	{
+	  "Protections": [
+	    {
+	      "Name": "AntiILdasm",
+	      "Enabled": false
+	    },
+	    {
+	      "Name": "AntiDe4dot",
+	      "Enabled": false
+	    },
+	    {
+	      "Name": "ObjectReturnType",
+	      "Enabled": false
+	    },
+	    {
+	      "Name": "NoNamespaces",
+	      "Enabled": false
+	    },
+	    {
+	      "Name": "FullRenamer",
+	      "Enabled": false
+	    },
+	    {
+	      "Name": "AntiDebugBreakpoints",
+	      "Enabled": false
+	    },
+	    {
+	      "Name": "StringsEncryption",
+	      "Enabled": false
+	    },
+	    {
+	      "Name": "UnmanagedString",
+	      "Enabled": false
+	    },
+	    {
+	      "Name": "DotNetHook",
+	      "Enabled": false
+	    },
+	    {
+	      "Name": "CallToCalli",
+	      "Enabled": false
+	    },
+	    {
+	      "Name": "AntiDecompiler",
+	      "Enabled": true
+	    },
+	    {
+	      "Name": "BitMethodDotnet",
+	      "Enabled": true
+	    },
+	    {
+	      "Name": "BitTimeDateStamp",
+	      "Enabled": true
+	    },
+	    {
+	      "Name": "BitDotNet",
+	      "Enabled": true
+	    },
+	    {
+	      "Name": "BitMono",
+	      "Enabled": true
+	    }
+	  ]
+	}

docs/developers/protection-runtime-moniker.rst

@@ -71,4 +71,14 @@ Specify Rust Runtime Moniker Attribute.
 
 	[UsedImplicitly]
 	[RuntimeMonikerRust] // Add this Attribute which says this protections works only with Rust Runtime
-	public class RustPacker : Packer // or instead use Protection or PipelineProtection
+	public class RustPacker : Packer // or instead use Protection or PipelineProtection
+
+
+
+After that user need to use the ``RustPacker`` and they will receive an message that the ``RustPacker`` "is intended for Rust runtime".
+
+
+
+.. note::
+
+	You don't need to make any services registration or instance creation for the ``RuntimeMonikerRust`` due to it will get the attribute automatically behind the hood using Reflection, and Protections Info Output in the Console/GUI (whatever is used, user will get a message notification about that). So, you don't need to care about ``RuntimeMonikerRust`` anymore, simply add it on top of the feature and have fun!

docs/index.rst

@@ -43,12 +43,21 @@ Table of Contents:
    developers/configuration
 
 
+.. toctree::
+   :maxdepth: 1
+   :caption: Obfuscation Issues
+   :name: sec-obfuscationissues
+
+   obfuscationissues/corlib-not-found
+
+
 .. toctree::
    :maxdepth: 1
    :caption: Best Practices
    :name: sec-bestpractices
 
    bestpractices/bitmono-combo
+   bestpractices/zero-risk-obfuscation
 
 
 .. toctree::

docs/obfuscationissues/corlib-not-found.rst

@@ -0,0 +1,11 @@
+CorLib not found
+================
+
+The problem
+-----------
+You're getting an error it says: `Could not load file or assembly CorLib Version=x.x.x.x, etc` 
+
+
+Solution
+--------
+The thing that may cause this issue is that you're running on .NET Framework (the obfuscator project) and the actual obfuscator project is running on .NET Core (let's say - 6.0), and you're trying to run the obfuscated file on Mono, you might already catch the problem, you need to change the obfuscator project TargetFramework (i.e in this case to .NET Framework) to approximately the same version as target file for obfuscation.

docs/protections/antide4dot.rst

@@ -3,4 +3,9 @@ AntiDe4dot
 
 How it works?
 -------------
-Protection adds multiple attributes of known obfuscators/protectors and as a result fools de4dot.
+Protection adds multiple attributes of known obfuscators/protectors and as a result fools de4dot.
+
+
+.. warning::
+
+    Due to protection is not really powerful and widely known by most reversers and skids, on GitHub you may see a lot of solutions to destroy this protection.

docs/protections/antidecompiler.rst

@@ -10,4 +10,4 @@ That means if someone will try to analyze the protected nested type, dnSpy will
 
 .. warning::
 
-    This protection is only compatible with Mono.
+    This protection compatible only with Mono.