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 macOS

macOS to Windows

How to install NoPorts when connecting from macOS to Windows

PreviousmacOS to LinuxNextConnecting from 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 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 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

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>_client with your client atSign.

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

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

Run the same command, but for your device atSign.

Replace @<REPLACE>_device with your device 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 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>_device with your device atSign.

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

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 . 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 pick a device name, and click Next. You will need to enter this device name in Step 7.

5.3 If you wish to add additional arguments to pass 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>_device with your device atSign,

@<REPLACE_NAME> with the unique device name from Step 5.

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

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