> For the complete documentation index, see [llms.txt](https://docs.noports.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.noports.com/installation-faq/reuse-your-client-atsign-on-another-machine.md).

# Reuse your client Atsign on another machine

A review of two available methods

## Want to use your Atsign on a different machine?

You can:

A. Generate a new set of cryptographic keys (Recommended)

B. Copy the cryptographic keys from the machine where it's been activated in the past (Not recommended)

### **Option A) Generate a new set of cryptographic keys (Recommended)**

To generate a new set of cryptographic keys, there are three main steps. They occur from two different machines, so pay careful attention to which machine you perform each step on.

"Old machine" is the machine that has the **original** set of cryptographic keys that were generated. "New machine" is the device you want the new set of cryptographic keys on. These new keys will have restricted permissions that only work with NoPorts, and cannot be used for generating other keys.

1. \[Old machine] Generate a Passcode
2. \[New machine] Enroll the new key pair (send a request for keys from the new machine)
3. \[Old machine] Approve the request

**For detailed instructions, follow this guide:**

{% content-ref url="/pages/XyWfPHHRFggzmCNpS40d" %}
[Generate a new set of cryptographic keys](/installation-faq/reuse-your-client-atsign-on-another-machine/generate-a-new-set-of-cryptographic-keys.md)
{% endcontent-ref %}

### **Option B) Copy the cryptographic keys from the machine where it's been activated in the past (Not recommended)**

* The Atsign keys file will be located at `~/.atsign/keys/` directory with a filename that will include the Atsign. Copy this file from your other machine to the same location on the machine that you are installing SSH No Ports on, using `scp` or similar.

Why don't we recommend this approach?

> When you use method A, it creates a new set of cryptographic keys. These keys can be disabled individually, which means if a device's keys are compromised, you can disable those keys without affecting your other devices.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.noports.com/installation-faq/reuse-your-client-atsign-on-another-machine.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.