> For the complete documentation index, see [llms.txt](https://dmcxblue.gitbook.io/red-team-notes-2-0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dmcxblue.gitbook.io/red-team-notes-2-0/red-team-techniques/persistence/t1098-account-manipulation/ssh-authorized-keys.md).

# SSH Authorized Keys

Adversaries may modify the SSH authorized\_keys file to maintain persistence on a victim host. Linux distributions and macOS commonly use key-based authentication to secure the authentication to secure the authentication process of SSH sessions for remote management. The authorized\_keys file in SSH specifies the SSH keys that can be used for logging into the user's home directory under \<user-home>/.ssh/authorized\_keys. Users may edit the system's SSH config file to modify the PubKeyAuthentication and RSAAuthentication to the value "yes" to ensure public key and RSA authentication are enabled. The SSH config file is usually located under /etc/ssh/sshd\_config

This technique works when the PUBLIC key has been allowed in the authorized\_keys file

<figure><img src="/files/n4l9YVucpMi5UTpa2u7B" alt=""><figcaption></figcaption></figure>

Also the sshd\_config file needs to have the PubKeyAuthentication as "YES"

<figure><img src="/files/2lN8uMVi60Ls1b1BJa4r" alt=""><figcaption></figcaption></figure>

When all has been set the malicious actor can steal the private key, or modify the authorized\_keys file to add a new key which allows the attacker to remote onto the workstation via SSH

<figure><img src="/files/a1lbfd67zIjVIxnI0HIK" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dmcxblue.gitbook.io/red-team-notes-2-0/red-team-techniques/persistence/t1098-account-manipulation/ssh-authorized-keys.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
