> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/walkthroughs/using-sftp-ssh-keys/how-to-encrypt-decrypt-a-private-key.md).

# How to encrypt/decrypt a private key

Private keys can be encrypted with a password for additional security. Learn how to encrypt and decrypt a private key.

## Encrypt a private key on MacOS or Linux

#### **1. Check if Your Key Is Already Encrypted**

Private keys are usually stored in `~/.ssh/`. To check:

```bash
cat ~/.ssh/id_rsa
```

* If you see `ENCRYPTED` in the header (like `-----BEGIN OPENSSH PRIVATE KEY-----` with `ENCRYPTED` noted), then it’s already passphrase-protected.
* If not, you can encrypt it.

***

#### **2. Encrypt or Change the Passphrase**

```bash
ssh-keygen -p -f ~/.ssh/id_rsa
```

* `-p` → prompts you to change the passphrase.
* `-f` → specifies the key file.

You’ll be asked for:

1. The old passphrase (press **Enter** if none exists).
2. A new passphrase (twice, for confirmation).

This adds strong encryption to your private key file.

***

Now your private key is safely encrypted with a passphrase.

## Decrypt a private key in MacOS or Linux

Decrypting a RSA private key can be done using a single command

```bash
ssh-keygen -p -f ~/.ssh/id_rsa -N ""
```

You will be prompted for the current passphrase. Do not pass the old passphrase on the command line (it would be visible in process lists).


---

# 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.couchdrop.io/walkthroughs/using-sftp-ssh-keys/how-to-encrypt-decrypt-a-private-key.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.