Update cheatsheets

This commit is contained in:
ivuorinen
2025-01-26 00:17:15 +00:00
parent 068c24ac65
commit 463eefab17
6 changed files with 124 additions and 2 deletions

29
tldr/bloodhound-python Normal file
View File

@@ -0,0 +1,29 @@
---
syntax: markdown
tags: [tldr, common]
source: https://github.com/tldr-pages/tldr.git
---
# bloodhound-python
> A Python ingestor for BloodHound, used to enumerate Active Directory relationships.
> More information: <https://github.com/dirkjanm/BloodHound.py>.
- Collect all data using default collection methods (includes groups, sessions, and trusts):
`bloodhound-python --username {{username}} --password {{password}} --domain {{domain}}`
- Collect data using Kerberos authentication without requiring a plaintext password:
`bloodhound-python --collectionmethod {{All}} --kerberos --domain {{domain}}`
- Authenticate using NTLM hashes instead of a password:
`bloodhound-python --collectionmethod {{All}} --username {{username}} --hashes {{LM:NTLM}} --domain {{domain}}`
- Specify a custom name server for DNS queries:
`bloodhound-python --collectionmethod {{All}} --username {{username}} --password {{password}} --domain {{domain}} --nameserver {{nameserver}}`
- Save the output files as a compressed ZIP archive:
`bloodhound-python --collectionmethod {{All}} --username {{username}} --password {{password}} --domain {{domain}} --zip`

30
tldr/byobu Normal file
View File

@@ -0,0 +1,30 @@
---
syntax: markdown
tags: [tldr, common]
source: https://github.com/tldr-pages/tldr.git
---
# byobu
> Window manager and terminal multiplexer.
> See also: `tmux` and `screen`.
> More information: <https://www.byobu.org/documentation>.
- Start a new session:
`byobu`
- Configuration and help:
`byobu-config`
- Select tmux (default) or screen backend:
`byobu-select-backend`
- Enable automatic startup after login into text console:
`byobu-enable`
- Disable automatic startup after login into text console:
`byobu-disable`

View File

@@ -11,7 +11,7 @@ source: https://github.com/tldr-pages/tldr.git
- Initialize `kde-builder`:
`kde-builder --initial-setup`
`kde-builder --generate-config && kde-builder --install-distro-packages`
- Compile a KDE component and its dependencies from the source:
@@ -27,7 +27,7 @@ source: https://github.com/tldr-pages/tldr.git
- Resume compilation from a specific dependency:
`kde-builder --resume-from={{dependency_component}} {{component_name}}`
`kde-builder --resume-from {{dependency_component}} {{component_name}}`
- Run a component with a specified executable name:

29
tldr/mpremote Normal file
View File

@@ -0,0 +1,29 @@
---
syntax: markdown
tags: [tldr, common]
source: https://github.com/tldr-pages/tldr.git
---
# mpremote
> Remotely control MicroPython devices.
> More information: <https://docs.micropython.org/en/latest/reference/mpremote.html>.
- List all connected MicroPython devices:
`mpremote connect list`
- Open an interactive REPL session with a connected device:
`mpremote connect {{device}}`
- Run a local script on a connected device:
`mpremote run {{path/to/script.py}}`
- Mount a local directory to the device:
`mpremote mount {{path/to/directory}}`
- Install a mip package on the device:
`mpremote mip install {{package}}`

26
tldr/proxify Normal file
View File

@@ -0,0 +1,26 @@
---
syntax: markdown
tags: [tldr, common]
source: https://github.com/tldr-pages/tldr.git
---
# proxify
> A versatile and portable proxy for capturing, manipulating, and replaying HTTP/HTTPS traffic on the go.
> See also: `mitmproxy`.
> More information: <https://github.com/projectdiscovery/proxify>.
- Start a HTTP proxy (on the loopback network interface `127.0.0.1` port `8888`):
`proxify`
- Start a HTTP proxy on a custom network interface and port (may require `sudo` for a port number lower than `1024`):
`proxify -http-addr "{{network_interface}}:{{port_number}}"`
- Specify output format and output file:
`proxify -output-format {{jsonl|yaml}} -output {{path/to/file}}`
- Display help:
`proxify -h`

View File

@@ -23,3 +23,11 @@ source: https://github.com/tldr-pages/tldr.git
- Forward incoming data of a local port to another host and port:
`sudo socat TCP-LISTEN:80,fork TCP4:www.example.com:80`
- Send data with multicast routing scheme:
`{{echo "Hello Multicast"}} | socat - UDP4-DATAGRAM:{{224.0.0.1}}:{{5000}}`
- Receive data from a multicast:
`socat - UDP4-RECVFROM:{{5000}}`