Skip to content

About

Standalone, fully configurable rooted SSH (Dropbear) server for KernelSU/APatch/Magisk. WebUI, hidden banner, BFU/AFU, bundled sftp-server/scp/rsync. Root by default, or a lower-privilege account.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

21 stars

Watchers

6 watching

Forks

Latest commit

 

History

73 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

VD Dropbear

VD Dropbear

License KernelSU APatch Magisk Stars Release

Releases · Wiki · User guide · Configuration · Architecture · AI agents · Changelog · XDA thread

Languages: English · العربية · Čeština · Deutsch · Español · فارسی · Français · हिन्दी · Bahasa Indonesia · Italiano · 日本語 · 한국어 · Nederlands · Polski · Português · Русский · Svenska · ไทย · Türkçe · Українська · Tiếng Việt · 中文

A standalone, fully configurable Dropbear SSH server packaged as a KernelSU / APatch / Magisk module. It launches on its own and depends on no other module.

⚠️ A login defaults to a full ROOT shell. Treat this like the keys to the device: prefer public keys over passwords, and keep the port off the public Internet.

Why

Android's built-in way to get a shell on your own phone is ADB (USB debugging), and turning it on is invasive and self-exposing. adb_enabled and development_settings_enabled are world-readable settings; any app, SDK or anti-fraud / RASP library can read them, the connection is logged, and there is no supported way to hide that ADB is, or ever was, enabled. The exposure follows you even on a stock, non-rooted phone: to get a shell, you have to announce it.

VD Dropbear is the private alternative. On a rooted device it gives you a real SSH server (root shell, SFTP and rsync over the network) with no adb_enabled tell, no USB-debugging flag, a version banner that reveals nothing, and credentials you control. Your access stays yours, instead of a globally-readable "I am being debugged" flag that anything on the device can read.

Features

  • One daemon, always. It starts at boot and from the manager's Action button, and you can start / stop / restart it from the WebUI at any time; never more than one instance.
  • Everything is configurable from the WebUI (or /data/adb/vddropbear/config):
    • port, and bind to loopback / all / IPv4 / IPv6 / specific addresses
    • start before first unlock (BFU) or only after it (AFU), a single toggle
    • public-key and/or password authentication, max auth tries
    • login shell, HOME, extra environment
    • idle timeout, keepalive, receive window
    • local / remote port forwarding and gateway ports (all off by default)
    • host-key type (ed25519 / rsa / ecdsa)
  • Hidden version banner. The SSH protocol requires a banner, so it cannot be removed, but VD Dropbear replaces it with an uninformative one so scanners cannot fingerprint the exact server or version and aim known-version attacks at it.
  • Secrets stored sensibly (see Security model).
  • Bring your own credentials. Add authorized keys and password accounts. A login runs as the account you authenticate as: root by default, or a lower-privilege Android account (shell, system). The WebUI enforces a minimum password strength and never stores a password in clear text.
  • File transfer and sync built in. The bundle ships sftp-server, scp and rsync, so SFTP, sshfs, GUI clients and backups all work over the same connection.
  • SSH over USB, no ADB. Turn on USB tethering and bind the daemon to the USB address: the same session over the cable, faster and steadier than wifi for large transfers.
  • Every device and emulator. arm64-v8a, armeabi-v7a, x86, x86_64.

AI agents on your device

A standing SSH endpoint turns your phone into something an autonomous AI agent can operate directly. Any agent that can drive a shell or an SSH connection (Claude Code, aider, an LLM-in-the-loop script, your own automation) gets a real root session on the device, over the network, with no USB tether and none of ADB's self-exposing debug flags. The agent sees a normal Linux-like shell and can:

  • read and edit files, flip settings, and manage modules, packages and services;
  • triage logs, pull artifacts, and run diagnostics or forensics on demand;
  • move and sync files both ways over scp / sftp / rsync, for backups, migrations or provisioning;
  • drive a whole fleet of rooted devices from one place, each reachable by its own key.

Because the project is built to be AI-friendly, with a documented configuration file, an explicit runtime env contract, predictable paths and plain-text status, an agent can discover how to use it without guesswork.

Root by default, so treat it like root. A default login lands as root, and you can also log in as a lower-privilege account (shell, system); see the warning below. When you hand access to an agent, give it its own credential (not your personal key), point it at a lower-privilege account like shell if you want to limit its reach, scope the binds to the networks you trust (loopback or a VPN rather than the open internet), keep password auth off, and remember you can revoke a key or stop the daemon at any time from the WebUI.

Install

Flash the module zip in the KernelSU, APatch or Magisk manager (or from the command line with ksud module install / apd module install), open the module's WebUI to set the port and add your keys, then reboot (or press Action to start it now).

Security model

Where secrets live: BFU vs AFU

/data/adb is device-encrypted (DE) storage: it is decrypted before the user unlocks the phone (Before First Unlock), so anything there is readable pre-unlock. /data/misc_ce is credential-encrypted (CE): Android keeps it encrypted until the user unlocks (After First Unlock).

  • AFU mode (default, START_IN_BFU=0): the daemon waits for unlock and reads its host key, authorized_keys and password hashes from CE storage. Maximum protection; SSH works only after the device has been unlocked once since boot.
  • BFU mode (START_IN_BFU=1): the daemon starts before unlock so you can SSH in early (for example, to unlock the device remotely). Its secrets then live on DE storage and are readable before unlock, a deliberate and documented trade-off. Enable it only if you need pre-unlock SSH.

We deliberately do not add our own encryption on top of CE: it is already encrypted with the user's credential, and layering another cipher would need a key that has to live somewhere (on DE it would be exposed; deriving it from the user credential just re-implements CE). That would buy a false sense of security, not real protection.

Passwords

Password login is off by default, because a login defaults to root and keys are far safer. When you do set a password, the WebUI enforces a minimum strength and stores only a hash, never clear text.

Build

The server binary is built by CI from upstream mkj/dropbear with a small, auditable patch set (see patches/): a neutral/configurable identity string, config-driven paths for authorized_keys and the password file, and the Android openpty fix for interactive PTYs. A scheduled workflow tracks upstream and rebuilds, so the module stays current. See .github/workflows/ and CONTRIBUTING.md.

Incremental updates (VDLU)

VD Dropbear ships the VDLU engine (vendored in vdlu/): the module updates itself by fetching only the files that changed (content-addressed blobs + a signed manifest.json), instead of re-downloading the whole .zip. Hardened profile: the ed25519 signature is mandatory and downgrades are blocked; the full .zip stays valid as a fallback.

  • LIVE-only (no reboot): updates apply on the next boot via service.sh (setsid, backgrounded, never stalling boot), a no-op when no feed is reachable.
  • State in /data/adb/<module>/vdlu/, outside the module, so it survives a reflash.
  • WebUI: an Updates panel with a progress toast and cancel; auto-update is opt-in.

Documentation

Every wiki page is also translated into each language in the switcher above; the same sources live under docs/.

See also

Sibling projects by the same author:

  • VDInfos: a device method debugger that reads each item through every method that can read it and compares them side by side.
  • VDGoogle: reads what Google records on your device about RCS, Wallet and Play Integrity, fully on-device and with no internet.
  • VDBackup: full app and data backup and restore as root, driven entirely from a WebUI.
  • COPG-VD: a device spoofer that turns a fresh fingerprint into a coherent, consistent profile.

Contacts

License

VD Dropbear's own code is Apache-2.0; see LICENSE. The module also bundles third-party binaries: Dropbear (MIT-style), OpenSSH's sftp-server and scp (BSD), and rsync (GPL-3.0), each under its own license; see THIRD-PARTY-NOTICES.md, including how we comply with the GPL for rsync. Our Apache-2.0 code is unaffected (the GPL binary is merely aggregated, not linked).

Trademarks

VD Dropbear is an independent, unofficial project, not affiliated with or endorsed by any third party. "Android" is a trademark of Google LLC; "SSH" is a registered trademark of SSH Communications Security. VD Dropbear runs entirely on your device.

Tags

SSH Dropbear KernelSU Magisk APatch root sshd remote-access openssh-alternative Android BFU VD-dropbear

About

Standalone, fully configurable rooted SSH (Dropbear) server for KernelSU/APatch/Magisk. WebUI, hidden banner, BFU/AFU, bundled sftp-server/scp/rsync. Root by default, or a lower-privilege account.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

21 stars

Watchers

6 watching

Forks

Releases

Contributors

Languages