> For the complete documentation index, see [llms.txt](https://wiki.solids.group/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.solids.group/computing/ssh-public-keys.md).

# SSH Public Keys

Public keys let you use SSH without typing your server password every time.

## Generate a Key

On your local machine, run:

```bash
ssh-keygen
```

Press Enter to accept the default location. You may enter a passphrase or leave it blank.

This creates a `.ssh` directory in your home directory containing files similar to:

```
id_rsa
id_rsa.pub
```

The private key, `id_rsa`, must not be shared. The public key, `id_rsa.pub`, can be shared.

## Install the Public Key on a Server

Log in to the server, then create the `.ssh` directory and set its permissions:

```bash
mkdir .ssh
chmod 700 .ssh
cd .ssh
```

Create or open a file named `authorized_keys` and paste the contents of your public key into it.

Then set the file permissions:

```bash
chmod 600 authorized_keys
```

Log out and log back in using SSH. If you created the key with a passphrase, enter it when prompted. Otherwise, you should be logged in without typing your server password.


---

# 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://wiki.solids.group/computing/ssh-public-keys.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.