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
  • Step 1 to Step 4
  • Step 5 and Step 6
  • Step 7 and Step 8
  • Connecting more machines to your device atSign
Edit on GitHub
Export as PDF
  1. Installation
  2. Connecting from Windows

Windows to macOS

How to install NoPorts when connecting from Windows to macOS

PreviousConnecting from WindowsNextWindows to Linux

Last updated 13 days ago

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

Download the installer . Then unzip the file.

Launch the NoPortsInstaller.exe program and allow it administrative permissions. Click Client Install and follow the process until installation is complete.

Step 2: Activate your client atSign

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

Step 2.1 Click on Activate atSign.

Step 2.2 Enter the atSign you wish to activate and click Submit.

Step 2.3 Check your email for the OTP (one-time password), then enter it and press Generate.

Step 2.4 Once activated, the master keys will save at ~/.atsign/keys. Wait for the keys to generate, then go back Home.

Step 3: Activate your device atSign

Repeat the activation process, but for your device atSign. The device master keys will also save at ~/.atsign/keys.

Step 4: Generate an atSign authorization passcode for your device atSign

Follow the steps below to generate a 6-character one-time passcode which you will use in Step 6.

4.1 Click Manage Keys.

4.2 Enter your device atSign and click Next.

4.3 Click New OTP.

4.4 Wait a few seconds for the OTP to appear then proceed to Step 5 on the machine you are connecting to.

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

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

Step 6: Initiate atSign authorization request

Run the following command to make an authorization request.

Be sure to replace the following values:

@<REPLACE>_device with your device atSign,

<PASSCODE> with the passcode generated in Step 4,

@<REPLACE>_device_key with your device atSign,

<DEVICE_NAME> with a unique name for the machine you are on

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

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

Click Refresh and the new request will appear.

  • If the request looks incorrect, press Deny to deny it and start the process again.

  • If the request looks correct, press Approve to approve it.

Once approved, the request will disappear from the list. On the machine you are connecting to, it will take a few seconds to process the approval.

Step 8: Use NoPorts!

That's it. You can start using NoPorts or explore some of the .

Connecting more machines to your device atSign

To connect more machines to your device atSign, repeat Steps 4 through 7.

from GitHub
use cases available here