> 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/cms/duplicati-cms-exploitation/duplicati-backup-reading-files.md). # Duplicati - Reading backup files Duplicati backup abuse notes for backup destination control, host-mounted source directories, sensitive file restore, SSH key recovery, and data exfiltration.
With access to the **Duplicati admin panel**, create a new backup to exfiltrate the **SSH key**.
**Docker Configuration Analysis**/ The `docker-compose.yml` file shows that files are stored in the host system **source** directory, mounted into the container.
**Target Directory Selection**/ To access sensitive files, set the **backup** destination to that directory by selecting: * **Dossier source** : `/source/home/marcus/`
* **Source Data:** `source/root/`
**Configuration Finalization** * Save the configuration.
* Run the **backup** to recover the targeted files.
### Extracting Backed Up Files After the **backup** runs, three ZIP archives are generated.
* **File access** * Directly opening the files fails because of access restrictions. * Through **Duplicati**, use **Restore Files** to recover the content.
**Restore and Exfiltration** * Extract files from the backup.
Select **`/source/home/marcus/`** as the restore source.
--- # 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/cms/duplicati-cms-exploitation/duplicati-backup-reading-files.md?ask=&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.