# Username bruteforcing
### Discover username
* wordlist collection
* Web site info
* Image metadata
* Other information collected from the other machines
* ONIST
### Create a username list
#### Manual creation
```bash
# Change all lower to all upper
tr '[:lower:]' '[:upper:]' < users.txt >> users-updated.txt
# Change all upper cases to all lower cases
tr '[:upper:]' '[:lower:]' < users.txt > users-updated.txt
# Change the first letter only to upper in the string
cat users.txt | sed 's/./\U&/'
```
#### username-anarchy
```bash
#Create an initial list of users
James Roberts
Michale Chaffrey
Donald Klay
Sarah Osvald
Jeffer Robinson
Nicole Smith
# Then run the username-anarchy to create different username combinations
username-anarchy -i authors -f flast,lfirst,f.last > got_users.txt
```
#### Brutefocing usernames against a Kerberos service
{% code overflow="wrap" %}
```bash
nmap -p 88 --script=krb5-enum-users --script-args="krb5-enum-users.realm='essos.local',userdb=got_users.txt" 192.168.56.12
nmap -p 88 --script=krb5-enum-users --script-args="krb5-enum-users.realm='sevenkingdoms.local',userdb=got_users.txt" 192.168.56.10
```
{% endcode %}
---
# Agent Instructions: 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:
```
GET https://iptracej.gitbook.io/windows-linux-and-active-directory-ctf-notes/active-directory/user-recon/username-bruteforcing.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.