Languages: English · العربية · Čeština · Deutsch · Español · فارسی · Français · हिन्दी · Bahasa Indonesia · Italiano · 日本語 · 한국어 · Nederlands · Polski · Português · Русский · Svenska · ไทย · Türkçe · Українська · Tiếng Việt · 中文
VD Dropbear starts an SSH server, and every connection that successfully authenticates receives a root shell. The security of your device therefore equals the security of this server's configuration and credentials. Please:
- Prefer public keys over passwords. Password login is off by default.
- If you must use a password, use a strong one; the WebUI enforces a minimum and stores only a hash.
- Do not expose the port to the public Internet. Bind to loopback or a trusted LAN, or reach it over a VPN / tunnel.
- Understand the BFU trade-off: enabling start-before-unlock places the host key and credentials on device-encrypted storage, readable before the device is unlocked. Leave it off unless you need pre-unlock SSH.
- Keep forwarding off unless you need it (it is off by default).
- A neutral, uninformative version banner so network scanners cannot fingerprint the exact server and version.
- Credentials on credential-encrypted storage by default (decrypted only after you unlock).
- No telemetry, no network calls of its own, no analytics. It runs entirely on your device.
Security fixes land on the latest release. The server binary tracks upstream Dropbear; upstream security releases are rebuilt and shipped as soon as the CI picks them up.
Please report security issues privately, not in a public issue:
- E-mail: vd.priv8@pm.me
- Telegram: @VD_Priv8
Include the version, a description, and (ideally) a reproduction. You will get an acknowledgement, and we will coordinate a fix and disclosure timeline with you. For vulnerabilities in Dropbear itself, please also report upstream at https://matt.ucc.asn.au/dropbear/.
This documentation was generated with Claude (Anthropic) and is maintained by VD171. Corrections and improvements are welcome; see CONTRIBUTING.md.