> For the complete documentation index, see [llms.txt](https://www.kryptor.co.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.kryptor.co.uk/tutorial.md).

# Tutorial

{% hint style="info" %}
Some common example commands are listed below. For step-by-step instructions, advice/warnings, and additional functionality, please see the different [sections](/tutorial/entering-a-passphrase.md).
{% endhint %}

## tldr

* Encrypt a file/directory with a passphrase:

```bash
kryptor --encrypt --passphrase "path/to/unencrypted_file"
```

* Decrypt an encrypted file with a passphrase:

```bash
kryptor --decrypt --passphrase "path/to/encrypted_file"
```

* Generate a new key pair (stored in `~/.kryptor`) for encryption or signing:

```bash
kryptor --generate
```

* Encrypt a file/directory to one or more recipient public keys:

{% code overflow="wrap" fullWidth="false" %}

```bash
kryptor --encrypt --public Cu//0bQcNYsWeSMwh+sZlJjDIRajfxn65x0qY0MHanPAjlk= --public Cu//Rwvoo8l1x0/bn6yg3p2+SMWSzKhDdPqvlYRFLNaaFSU= "path/to/unencrypted_file"
```

{% endcode %}

* Decrypt a file sent to your public key using your default private key and the sender's public key:

{% code overflow="wrap" %}

```bash
kryptor --decrypt --public Cu//2M5FqAnxmW7PiKxIqLmKEPNxT1Kdkm4U3K/Gr++6OAQ= "path/to/encrypted_file"
```

{% endcode %}

* Sign a file with your default private key:

```bash
kryptor --sign "path/to/unsigned_file"
```

* Verify a signature using someone's public key:

{% code overflow="wrap" %}

```bash
kryptor --verify --public Ed//bnY+xqUXVMaaI0poBwTqDRlKA9+x9FjlDAHE9MmXKG4= "path/to/signed_file"
```

{% endcode %}


---

# 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://www.kryptor.co.uk/tutorial.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.