> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/ja/ports-and-services/ssh-22.md).

# SSH - 22

ブルートフォーステスト、ユーザー列挙、鍵ベースアクセス、認証情報検証のためのSSH列挙ノート。

SSH は通常、認証とアクセスのためのサービスです: 認証情報は慎重にテストし、旧来のユーザー列挙の問題を確認し、書き込み可能な `authorized_keys` パスが利用できる場合。

## メモ

<table data-view="cards" data-full-width="false" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>ブルートフォース</strong></td><td>Hydra で SSH 認証情報を検証する。</td><td><a href="/ja/ports-and-services/ssh-22/ssh-brute-force-attack.md">SSH - ブルートフォース攻撃</a></td></tr><tr><td><strong>ユーザー列挙</strong></td><td>旧来の OpenSSH のユーザー列挙の挙動を確認する。</td><td><a href="/ja/ports-and-services/ssh-22/ssh-user-enumeration-less-than-7.7-attack.md">SSH - ユーザー列挙（&lt; 7.7）</a></td></tr><tr><td><strong>キーによるアクセス</strong></td><td>書き込みアクセスがある場合は、SSH 公開鍵を authorized_keys に追加する。</td><td><a href="/ja/ports-and-services/ssh-22/ssh-id-rsa-key-creation.md">SSH - id/_rsa鍵の作成</a></td></tr></tbody></table>


---

# 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://hacking-notes.jord4n.pro/ja/ports-and-services/ssh-22.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.