Linux to Windows
How to install NoPorts when connecting from Linux to Windows
Step 1 to Step 4
These initial steps set up the machine initiating the connection.
On the machine you are connecting from
In this installation guide, @example01_np
will represent the client atSign, while @example02_np
will represent the device atSign.
Step 1: Download and run the Installer
Download the installer from GitHub by running the following command:
curl -L https://github.com/atsign-foundation/noports/releases/latest/download/universal.sh -o universal.sh
To check if the installation downloaded correctly:
stat universal.sh
Make the script executable and run the script by running the command below:
chmod u+x universal.sh
./universal.sh
You may be asked to enter your password if your machine requires sudo privileges.
The install type
Enter
client
when prompted.
Your atSigns (Skip this step)
To skip this step, simply press the Enter/Return key twice. Your atSigns will be activated in the upcoming steps.
Step 2: Activate your client atSign (@example01_np)
If you've already activated your client atSign on another device, this step will not work. Instead, follow this guide: Reuse your client atSign on another machine
This command activates your atSign and prompts you to enter an OTP. This is only done during the setup of a brand new atSign.
Replace @<REPLACE>_np
with your client atSign.
~/.local/bin/at_activate -a @<REPLACE>_np
Enter the one-time password (OTP) & Check your SPAM/PROMOTIONS folders
at_activate will pause and wait for the input of a one-time pin (OTP) sent to your email or phone number.
Once activated, the master keys will save at ~/.atsign/keys
.
Step 3: Activate your device atSign (@example02_np)
Run the same command, but for your device atSign.
Replace @<REPLACE>_np
with your device atSign.
~/.local/bin/at_activate -a @<REPLACE>_np
Enter the one-time password (OTP) & Check your SPAM/PROMOTIONS folders
at_activate will pause and wait for the input of a one-time pin (OTP) sent to your email or phone number.
Once activated, the master keys will save at ~/.atsign/keys
.
Step 4: Generate an atSign authorization passcode for your device atSign
Run the following command to generate a 6-character one-time passcode. You will use this passcode in Step 6.
Replace @<REPLACE>_np
with your device atSign.
~/.local/bin/at_activate otp -a @<REPLACE>_np
Step 5 and Step 6
After setting up the machine you're connecting from, you'll configure the machine you're connecting to.
On the machine you are connecting to
Step 5: Download and run the Installer
Download the installer from GitHub. Then unzip the file.
Install the Device Software
5.1: Click Device Install

5.2 :Enter both of your atSigns into the associated fields, then enter the name of the machine you are on into the a device name field, and click Next. You will need to enter this device name in Step 7.

5.3: (Optional) If you wish to add additional arguments to pass to sshnpd, enter them, then click Next.

5.4: Wait for the installation to complete, then click Next.
Step 6: Initiate atSign authorization request
You will see the following screen. Enter the one-time passcode generated in Step 4 on the machine you are connecting from. Then click Generate.

Step 7 and Step 8
With both machines now configured, the final steps bring us back to the machine initiating the connection.
On the machine you are connecting from
Step 7: Approve the atSign authorization request
Run the following command:
Be sure to replace the following values:
@<REPLACE>_np
with your device atSign,
@<REPLACE_NAME>
with the device name from Step 5.
~/.local/bin/at_activate approve -a @<REPLACE>_np --arx noports --drx <DEVICE_NAME>
Step 8: Use NoPorts!
That's it. You can start using NoPorts or explore some of the documented use cases, including MCP, SSH, RDP, SFTP, Web Server, and SMB.
Last updated