MacOS Device Installation

Choose the operating system which is running on your CLIENT machine:

Step 1 : Activate the device atSign from your CLIENT machine

If you've already activated the device atSign skip to step 2.

(1.1) Download the activation software on the client machine

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

(1.2) Run the installer

Make the script executable and run the script.

chmod u+x universal.sh
./universal.sh

(1.3) Activate the device atSign from the client 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.

~/.local/bin/at_activate -a @<REPLACE>_device

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 management keys will be saved in ~/.atsign/keys.

Step 2 : Installing on the DEVICE machine

(2.1) Download the installer

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

(2.2) Run the installer

Make the script executable and run the script.

chmod u+x universal.sh
./universal.sh

Step 3: Authorizing the device atSign

(3.1) Generate a passcode from your client machine

Run the following command. It should output a 6-character passcode.

~/.local/bin/at_activate otp -a @<REPLACE>_device

(3.2) Make an authorization request from your device machine

~/.local/bin/at_activate enroll -a @<REPLACE>_device \
  -s <PASSCODE> \
  -p noports \
  -k ~/.atsign/keys/@<REPLACE>_device_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

(3.3) Approve the authorization request from your client machine

Run the following command

~/.local/bin/at_activate approve -a @<REPLACE>_device --arx noports --drx <DEVICE_NAME>

Step 1 : Activate the device atSign from your CLIENT machine

If you've already activated the device atSign skip to step 2.

(1.1) Download the activation software on the client machine

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

(1.2) Run the installer

Make the script executable and run the script.

chmod u+x universal.sh
./universal.sh

(1.3) Activate the device atSign from the client 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.

~/.local/bin/at_activate -a @<REPLACE>_device

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 management keys will be saved in ~/.atsign/keys.

Step 2 : Installing on the DEVICE machine

(2.1) Download the installer

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

(2.2) Run the installer

Make the script executable and run the script.

chmod u+x universal.sh
./universal.sh

Step 3: Authorizing the device atSign

(3.1) Generate a passcode from your client machine

Run the following command. It should output a 6-character passcode.

~/.local/bin/at_activate otp -a @<REPLACE>_device

(3.2) Make an authorization request from your device machine

~/.local/bin/at_activate enroll -a @<REPLACE>_device \
  -s <PASSCODE> \
  -p noports \
  -k ~/.atsign/keys/@<REPLACE>_device_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

(3.3) Approve the authorization request from your client machine

Run the following command

~/.local/bin/at_activate approve -a @<REPLACE>_device --arx noports --drx <DEVICE_NAME>

Step 1 : Activate the device atSign from your CLIENT machine

If you've already activated the device atSign skip to step 2.

(1.1) Download the activation software on the client machine

See the Windows CLI Client Installation

(1.2) Activate the device atSign from the client 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.

C:\\Program\ Files\\NoPorts\\at_activate.exe otp -a @<REPLACE>_device

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 management keys will be saved in ~\.atsign\keys.

Step 2 : Installing on the DEVICE machine

~/.local/bin/at_activate enroll -a @<REPLACE>_device \
  -s <PASSCODE> \
  -p noports \
  -k ~/.atsign/keys/@<REPLACE>_device_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

(3.3) Approve the authorization request from your client machine

Run the following command

C:\\Program\ Files\\NoPorts\\at_activate.exe approve -a @<REPLACE>_device --arx noports --drx <DEVICE_NAME>

Choose the operating system which is running on your CLIENT machine:

Step 1 : Activate the device atSign from your CLIENT machine

If you've already activated the device atSign skip to step 2.

(1.1) Download the activation software on the client machine

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

(1.2) Run the installer

Make the script executable and run the script.

chmod u+x universal.sh
./universal.sh

(1.3) Activate the device atSign from the client 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.

~/.local/bin/at_activate -a @<REPLACE>_device

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 management keys will be saved in ~/.atsign/keys.

Step 2 : Installing on the DEVICE machine

(2.1) Download the installer

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

(2.2) Run the installer

Make the script executable and run the script.

chmod u+x universal.sh
./universal.sh

Step 3: Authorizing the device atSign

(3.1) Generate a passcode from your client machine

Run the following command. It should output a 6-character passcode.

~/.local/bin/at_activate otp -a @<REPLACE>_device

(3.2) Make an authorization request from your device machine

~/.local/bin/at_activate enroll -a @<REPLACE>_device \
  -s <PASSCODE> \
  -p noports \
  -k ~/.atsign/keys/@<REPLACE>_device_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

(3.3) Approve the authorization request from your client machine

Run the following command

~/.local/bin/at_activate approve -a @<REPLACE>_device --arx noports --drx <DEVICE_NAME>

Step 1 : Activate the device atSign from your CLIENT machine

If you've already activated the device atSign skip to step 2.

(1.1) Download the activation software on the client machine

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

(1.2) Run the installer

Make the script executable and run the script.

chmod u+x universal.sh
./universal.sh

(1.3) Activate the device atSign from the client 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.

~/.local/bin/at_activate -a @<REPLACE>_device

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 management keys will be saved in ~/.atsign/keys.

Step 2 : Installing on the DEVICE machine

(2.1) Download the installer

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

(2.2) Run the installer

Make the script executable and run the script.

chmod u+x universal.sh
./universal.sh

Step 3: Authorizing the device atSign

(3.1) Generate a passcode from your client machine

Run the following command. It should output a 6-character passcode.

~/.local/bin/at_activate otp -a @<REPLACE>_device

(3.2) Make an authorization request from your device machine

~/.local/bin/at_activate enroll -a @<REPLACE>_device \
  -s <PASSCODE> \
  -p noports \
  -k ~/.atsign/keys/@<REPLACE>_device_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

(3.3) Approve the authorization request from your client machine

Run the following command

~/.local/bin/at_activate approve -a @<REPLACE>_device --arx noports --drx <DEVICE_NAME>

Step 1 : Activate the device atSign from your CLIENT machine

If you've already activated the device atSign skip to step 2.

(1.1) Download the activation software on the client machine

If you haven't already done so, download the installer from GitHub. Then unzip the file.

(1.2) Activate the device atSign from the client machine

Open the installer and click Activate atSign

Enter the device atSign and click Submit

A one-time password will be sent to your registered email address. Enter the OTP and then click Generate

Once activated, the keys will be saved in ~\.atsign\keys. You can go back to the installer home screen.

Step 2 : Installing on the DEVICE machine

(2.1) Download the installer

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

(2.2) Run the installer

Make the script executable and run the script.

chmod u+x universal.sh
./universal.sh

Step 3: Authorizing the device atSign

(3.1) Generate a passcode from your client machine

Open the installer and click on Manage Keys.

Enter the device atSign and click Next.

Click New OTP.

Wait a few seconds for the OTP to appear then proceed to the next step.

(3.2) Make an authorization request from your device machine

Run the following command on your remote device.

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

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

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

(3.3) Approve the authorization request from your client machine

Click Refresh and the new request will appear

If the request looks incorrect, then click "Deny" to deny it, and start the process again.

If the request looks correct, then click "Approve" to approve it.

Once the request has been approved, it should disappear from the list in the installer. The enrollment will complete on the remote device in a few seconds.

Last updated 6 months ago