> For the complete documentation index, see [llms.txt](https://kchuene.gitbook.io/data-communication-project/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kchuene.gitbook.io/data-communication-project/tuning-and-security/cowrie-user-db.md).

# Cowrie User-DB

Making fake credentials for cowrie ssh honeypot less obvious.

## Update the UserDB

Copy the `/cowrie/cowrie-git/etc/userdb.example` from the **Cowrie** container onto the host

{% code overflow="wrap" lineNumbers="true" %}

```
sudo docker cp cowrie:/cowrie/cowrie-git/etc/userdb.example ./userdb.txt 
```

{% endcode %}

Edit the `userdb.txt` to contain the following credentials sourced from `rockyou.txt` (alternatively `SecLists`)

{% code overflow="wrap" lineNumbers="true" %}

```
root:localadmin
```

{% endcode %}

The main change is to accept only a single yet common/cracked password for the `root` user (though you can add other users).

Copy the `userdb.txt` back into the container and restart the container

{% code overflow="wrap" lineNumbers="true" %}

```
sudo docker cp ./userdb.txt cowrie:/cowrie/cowrie-git/etc/userdb.txt
```

{% endcode %}

{% code overflow="wrap" lineNumbers="true" %}

```
sudo docker container restart cowrie
```

{% endcode %}

{% hint style="info" %}
Note that we save it as a `.txt` when copying it back; this will cause **Cowrie** to use it.
{% endhint %}


---

# 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://kchuene.gitbook.io/data-communication-project/tuning-and-security/cowrie-user-db.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.