Bytehide 6.1.0.5

ByteHide Shield Documentation

Table of Contents

• ByteHide Shield ⚡
• What is ByteHide Shield?
• Why ByteHide Shield for .NET application protection?
• How to Get Started with ByteHide Shield?
• ByteHide Commands
  • ByteHide Shield Commands
  • Authenticate with ByteHide CLI
  • Clear current API token
  • Check current session
• How to protect with ByteHide Shield?
  • Protection with configuration file
  • Protection without configuration file
• Protecting JavaScript Code in ASP.NET Projects

ByteHide Shield ⚡

ByteHide Shield is the most advanced and up-to-date obfuscator, which will assist you in protecting your .NET applications most efficiently. Once you have Shield in your system, you will never have to worry about the manipulation or theft of your data on the .NET applications. Shield will protect your brand while keeping the integrity and security of your .NET application algorithms and intellectual property. ByteHide Shield is compatible with .NET, Xamarin, UWP and .NET core.

What is ByteHide Shield?

Are you a .NET application user? If yes, you will have the protection of the applications in your mind. We have great news for you as we are offering you ByteHide Shield, one of the best .NET obfuscators in the market, which will increase the security of your applications and ensure all kinds of security protection from threats of any sort. ByteHide Shield is the most advanced .NET obfuscator equipped with the latest technologies, and it will never let any manipulation and data theft on your .NET applications.

Why ByteHide Shield for protection of .NET application?

Although there are many .NET obfuscators in the market, you should prefer ByteHide Shield. There are many possible answers to this question, but the one word which describes it in the best way is "Quality".

As we all know, there are many .NET frameworks for the applications, and ByteHide Shield is optimized with all of them, including the latest one. It has the optimization for the client-side applications like desktop applications, but it is also optimized for the WebApps, Blazor and Server-Hosted APIs. Such an advanced tool is not available in the market, and if you are searching for one, you must go with ByteHide Shield to ensure the protection of your .NET applications.

How to Get Started with ByteHide Shield?

The ByteHide CLI allows you to access Shield and other products with a single account, all you have to do is install the CLI.

ByteHide commands

All ByteHide commands can be run using the bytehide prefix in the terminal.

Use the following command to get an overview of all ByteHide commands:

bytehide --help

ByteHide Shield commands

All Shield commands can be run using the shield prefix in the terminal.

Use the following command to get an overview of all Shield commands:

bytehide shield --help

Authenticate with ByteHide CLI

bytehide login <PROJECT TOKEN>

Where <PROJECT TOKEN> should be the key that you have previously generated from your panel.

If we already had a session stored on our computer, it will be replaced by the new one.

Once our API token has been notified to be valid, you can freely use the ByteHide CLI.

Clear current API token

If you want to delete your stored account information, you can run the following command:

bytehide clear

Check current session

Optionally you can check if your API token is valid, it will inform you if it has expired or has been revoked.

To do this, use:

bytehide check

How to protect with ByteHide Shield?

Use the following command to get an overview of all ByteHide Shield Protect commands:

bytehide shield protect --help

Protection with configuration file

To protect an application with specific settings, you must use the protect command, this command will allow you to protect your application with the settings you want.

bytehide shield protect <APPLICATION PATH> <OUTPUT DIRECTORY PATH> -c <CONFIGURATION PATH>

Where:

• <APPLICATION PATH> it will be the full path of the application, i.e: c:\folder\app.exe
• <OUTPUT DIRECTORY PATH> it will be the directory where the protected application will be saved i.e:c:\folder\protected\app.exe.
• -c <CONFIGURATION PATH> it will be the full path of the Shield configuration, i.e: c:\folder\shield.config.json. Read about the settings in: Shield Configurations.

An example would be:

bytehide shield protect "c:\folder\app.exe" "c:\folder\protected\app.exe" "c:\folder\shield.config.json"

Protection without configuration file

If you want to protect an application without using a configuration file, you can use the --project-token and --preset command, this command will start an interactive flow asking you for the necessary values to protect your application.

bytehide shield protect "c:\folder\app.exe" "c:\folder\protected\app.exe" --project-token e34762f8-8ad6-0000-0000-000000000000 --preset "optimized"

Where:

• <APPLICATION PATH> it will be the full path of the application, i.e: c:\folder\app.exe
• <OUTPUT DIRECTORY PATH> it will be the directory where the protected application will be saved i.e:c:\folder\protected\app.exe
• --project-token it will be the project token, i.e: e34762f8-8ad6-0000-0000-000000000000
• --preset it will be the preset to use, i.e: optimized

Protecting JavaScript Code in ASP.NET Projects

ByteHide Shield also provides a way to obfuscate JavaScript code within ASP.NET projects, ensuring the security of client-side scripts.

Usage

To protect JavaScript code in ASP.NET projects, you can use the protect-asp-javascript command, which is part of the Shield command set. This command allows you to obfuscate both user-defined and core ASP.NET scripts.

Command Syntax

bytehide shield protect-asp-javascript <PROJECT PATH> --replace-project [options]

Command Description

bytehide shield protect-asp-javascript

• Description: Apply obfuscation to JavaScript files in your ASP.NET application. This command allows you to secure both user-defined and core ASP.NET scripts in a single execution, making it ideal for automated protection in your build process.

Command Arguments

• <PROJECT PATH>
  Description: Specifies the path of the ASP.NET application to be protected.

Command Options

• --replace-project
  Description: If set to true, the original project files will be replaced with the obfuscated versions.
  Default Value: false

• --obfuscate-aspcore
  Description: Indicates whether to obfuscate core ASP.NET scripts (e.g., webforms.js) in addition to user-defined scripts.
  Default Value: false

• --output-directory-prefix
  Description: Specifies a prefix for the output directory name where the obfuscated project will be saved.
  Default Value: null

• --output-directory
  Description: Specifies the path of the output directory where the obfuscated project will be saved. If not provided, a default directory will be used.
  Default Value: null

Protecting JavaScript Code (.js files)

ByteHide Shield also provides a way to obfuscate JavaScript files, ensuring the security of back-side / client-side scripts.

Usage

To protect JavaScript code in .js files, you can use the protect-javascript command, which is part of the Shield command set. This command allows you to obfuscate directly .js files in a folder.

Command Syntax

bytehide shield protect-javascript <FOLDER PATH> --replace-project [options]

Command Description

bytehide shield protect-javascript

• Description: Apply obfuscation to JavaScript files (.js) in a directory. This command allows you to secure both user-defined and core js scripts in a single execution, making it ideal for automated protection in your build process.

Command Arguments

• <PROJECT PATH>
  Description: Specifies the path of the folder where the .js files are located.

Command Options

• --replace-project
  Description: If set to true, the original folder files will be replaced with the obfuscated versions.
  Default Value: false

• --script-match
  Description: Indicates the regex pattern to match with the directory files. I.e you can specify *.js, or for example ^backend.*\.(js|xjs)$. Default Value: *.js

• --output-directory-prefix
  Description: Specifies a prefix for the output directory name where the obfuscated project will be saved.
  Default Value: null

• --output-directory
  Description: Specifies the path of the output directory where the obfuscated files will be saved. If not provided, a default directory will be used.
  Default Value: null

---

Explore more about the Shield CLI here