How to activate Net Reactor with the license file by using command line

Question

I did purchase the license of the .Net Reactor, but I couldn't find any documentation about how to activate the .Net Reactor to Full version by using command line.

1. The reason why I need to using command line to activate is because I try to implement the process into GitHub Actions.

Steps: Install .Net Reactor > Build Solution > Obfuscation

2. Another reason is MacOS does not have UI, everything is using terminal to execute the obfuscation process.

I'm using latest version, .Net Reactor 6.9.0.0 on Win and MacOs. I did try using option -licensed and -staticlicensefilename license.license But I dun have time to wait 14 days later to check the obfuscated dlls was expired or not. Or anyone know how to check the obfuscated dlls expiration?

Thanks

Im expecting someone who used .Net Reactor able to give some guideline on how to activate the .Net Reactor Full version on Window and MacOS by using command line.

Answer 1

Fresh update - Good news everyone! Eziriz team now have a special license for GitHub Actions. They provide it by a special request. This options is available to users who have updated their license to the most recent version 6.9.8. I've just tested this and it works, I'm now transitioning away from using self-hosted obfuscation agents.

Answer 2

Background (with cautionary note!)

Unfortunately, the official way to activate .NET Reactor on Linux / macOS is not documented and their support hasn't responded to email requests for the details. However, in the (unstaffed) support channel on google groups a user mentioned a website that can be used for activation.

CAUTION: From looking at the WHOIS information it appears that this site is legit but it would be great if Eziriz would chime in and confirm.

Here is screenshot of the activation site at the time of writing:

---

Instructions

1. Visit the .NET Reactor download page to download the Linux or macOS binary.

2. Unzip the binary.

3. Make it executable, e.g. chmod +x dotNET_Reactor

4. Obtain the Hardware ID (see section Finding the Hardware ID below for instructions).

5. Visit the activation site. You will need to supply:

   a. An email address for the license to be sent to.

   b. Your main license file, likely named license.license.

   c. The Hardware ID of the Linux / macOS machine.

6. You will very promptly be emailed a hardware specific license file, likely named license.v3lic.

7. If you place this in the same directory as the dotNET_Reactor executable, it will now run in full mode.

8. You can verify this by running ./dotNET_Reactor -licensed; echo $? and checking that 101 is not printed.

---

Finding the Hardware ID

To find the Hardware ID of your Linux/macOS machine, run the executable without any arguments:

me@mymachine ~ % ./dotNET_Reactor
     _  _  ___  _____    ___  ___    _     ___  _____   ___   ___
    | \| || __||_   _|  | _ \| __|  /_\   / __||_   _| / _ \ | _ \
  _ | .` || _|   | |    |   /| _|  / _ \ | (__   | |  | (_) ||   /
 (_)|_|\_||___|  |_|    |_|_\|___|/_/ \_\ \___|  |_|   \___/ |_|_\
                                          v6.9.0.0 - Demo Version

Hardware ID: XXXX-XXXX-XXXX-XXXX-XXXX

Answer 3

It remains to be seen if GitHub Action can emulate the right environment to support .Net Reactor.

That tool is normally used (and activated) in an Azure pipeline, like Eziriz.reactor-tool-task (changelog)

As .NET Reactor is Windows based a Windows build agent must be used. You can define a Windows agent in your pipelines YAML file the following way:

---

However, the OP sam adds in the comments:

The eziriz support did reply my email.
Unfortunately, they not support GitHub Actions yet, but it is their plan now.