LogoLogo
  • NoPorts Documentation
  • Getting Started
  • Installation
    • Quick Start from macOS or Windows
    • Connecting from macOS
      • macOS to macOS
      • macOS to Linux
      • macOS to Windows
    • Connecting from Linux
      • Linux to macOS
      • Linux to Linux
      • Linux to Windows
    • Connecting from Windows
      • Windows to macOS
      • Windows to Linux
      • Windows to Windows
    • Cloud Installation Guides
      • Automated Installation on Amazon Web Services (AWS)
      • Automated Installation on Google Cloud Platform (GCP)
      • Automated Installation on Microsoft Azure
      • Automated Installation on Oracle Cloud Infrastructure (OCI)
    • OpenWrt Installation Guide
    • Manual Installation Guides
      • Device Installation
        • Tmux session
        • Standalone Binaries
        • Systemd Unit
        • Headless
      • Client Installation
    • Custom OS/Device Installs
      • IPFire
    • Installs at Scale
    • Upgrading NoPorts Software
      • NoPorts Client Upgrade
      • NoPorts Daemon Upgrade
    • Available Releases
  • Use Cases
    • SSH
    • SFTP
    • RDP
    • Web Server
    • SMB
    • Be your own VPN
  • Usage
    • npt Usage
    • sshnp Usage
      • Client Additional Configuration
    • sshnpd configuration
      • Daemon Additional Configuration
  • Integrations
    • OpenSSH Config
    • PuTTY config
  • Resources
    • How to activate an atSign
    • Reuse your client atSign on another machine
      • Generate a new set of cryptographic keys
    • How to name a device
    • How to generate SSH keys
    • Why activate the device atSign on the client?
  • Product Information
    • The NoPorts Philosophy
    • NoPorts Desktop Application
    • NoPorts Policy Service
    • Frequently Asked Questions
    • How It Works
    • Under The Hood
    • Sequence Diagram
  • Related Pages
    • Main Site
    • GitHub
Powered by GitBook
On this page
  • Choose the operating system which is running on your CLIENT machine:
  • Choose the operating system which is running on your CLIENT machine:
Edit on GitHub
Export as PDF
  1. Installation
  2. Linux Installation Guide

Linux Device Installation

Last updated 9 days ago

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 .

(1.1) Download the activation software on the client machine

(1.2) Run the installer

(1.3) Activate the device atSign from the client machine

Step 2 : Installing on the DEVICE machine

(2.1) Download the installer

(2.2) Run the installer


Step 3: Authorizing the device atSign

(3.1) Generate a passcode from your client machine

(3.2) Make an authorization request from your device machine

(3.3) Approve the authorization request from your client machine

Step 1 : Activate the device atSign from your CLIENT machine

(1.1) Download the activation software on the client machine

(1.2) Run the installer

(1.3) Activate the device atSign from the client machine

Step 2 : Installing on the DEVICE machine

(2.1) Download the installer

(2.2) Run the installer


Step 3: Authorizing the device atSign

(3.1) Generate a passcode from your client machine

(3.2) Make an authorization request from your device machine

(3.3) Approve the authorization request from your client machine

Step 1 : Activate the device atSign from your CLIENT machine

(1.1) Download the activation software on the client machine

(1.2) Activate the device atSign from the client machine

Step 2 : Installing on the DEVICE machine

(3.3) Approve the authorization request from your client machine

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

Step 1 : Activate the device atSign from your CLIENT machine

(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

(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

(1.1) Download the activation software on the client machine

(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

(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.

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

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

See the Windows

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

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

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

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

from GitHub
step 2
step 2
step 2
step 2
step 2
step 2
CLI Client Installation

Run the following command

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

Run the following command

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

Run the following command

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

Make the script executable and run the script.

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

Make the script executable and run the script.

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

Make the script executable and run the script.

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

Make the script executable and run the script.

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

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.

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.

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

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

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

~/.local/bin/at_activate otp -a @<REPLACE>_device
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
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
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
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
~/.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
~/.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
~/.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

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.