For the complete documentation index, see llms.txt. This page is also available as Markdown.

macOS to macOS

How to install NoPorts when connecting from macOS to macOS

Prerequisite

Before starting the NoPorts installation, ensure you have at least two atSigns available. If you don’t yet have any atSigns, you can sign up for a NoPorts subscription or free trial at my.noports.com/no-ports-plans.

Step 1 to Step 4

These initial steps set up the machine initiating the connection.

On the machine you are connecting from

Step 1: Download and run the Installer

Open a terminal and 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)

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.

~/.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.

~/.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

Open a terminal and 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

During installation, you’ll be prompted to enter the following items:

You may be asked to enter your password if your machine requires sudo privileges.

The install type

  • Enter device when prompted.

Your atSigns

  • Client Atsign: e.g., @example01_np

  • Device Atsign: e.g., @example02_np

Your device name

  • This should be the name of the machine you're currently installing on.

Step 6: Initiate Atsign authorization request

Run the following command to make an authorization request:

~/.local/bin/at_activate enroll -a @<REPLACE>_np \
  -s <PASSCODE> \
  -p noports \
  -k ~/.atsign/keys/@<REPLACE>_np_key.atKeys \
  -d <DEVICE_NAME> \
  -n "sshnp:rw,sshrvd:rw"

Once you see this text, you're ready to continue to the next step.

Submitting enrollment request 
Enrollment ID: ---------------------
Waiting for approval; will check every 10 seconds

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:

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