[BUG] `install.sh` failed when installing Nim

[fukusuket]

Is there an existing issue for this?

• I have searched the existing issues

Empire Version

5.5.4

Python Version

3.10.12

Operating System

Ubuntu 22.04 LTS

Database

SQLite

Current Behavior

install.sh fails with the following error when running nimble.

[>] Do you want to install Nim and MinGW? It is only needed to generate a Nim stager (y/N)? y
...
choosenim-init: Downloading choosenim-0.8.4_linux_amd64
      Info: Version 1.6.12 already selected
choosenim-init: ChooseNim installed in /root/.nimble/bin
choosenim-init: You must now ensure that the Nimble bin dir is in your PATH.
choosenim-init: Place the following line in the ~/.profile or ~/.bashrc file.
choosenim-init:     export PATH=/root/.nimble/bin:$PATH
    Prompt: winim not found in any local packages.json, check internet for updated packages? -> [forced yes]
Downloading Official package list
    Success Package list downloaded.
       Tip: 7 messages have been suppressed, use --verbose to show them.
     Error: Package not found.

After executing the above, when I checked the version of nimble, it was as follows.

sudo /root/.nimble/bin/nimble -v
nimble v0.13.1 compiled at 2023-03-10 01:10:05
git hash: couldn't determine git hash

Expected Behavior

install.sh success.

Steps To Reproduce

1. Run install.sh according to the quickstart/installation
   1. git clone --recursive https://github.com/BC-SECURITY/Empire.git
   2. cd Empire
   3. ./setup/checkout-latest-tag.sh
   4. sudo ./setup/install.sh
2. Proceed through the installer until you are asked to install Nim
3. [>] Do you want to install Nim and MinGW? It is only needed to generate a Nim stager (y/N)? -> Enter y

Anything else?

Following issue also seemed to failed for the same reason.

• [BUG]nimble install -y winim zippy nimcrypto #551

The following issues have been fixed in Nimble 0.14.1.

• https://github.com/nim-lang/nimble/releases/tag/v0.14.1
• Fix #953 nim-lang/nimble#962

[fukusuket]

I have confirmed that this issue does not occur with the following other installation methods.

• Kali Linux
• Docker

Therefore, this issue only occurs when installing using install.sh