Skip to content

FILE STRUCTURE

github-actions[bot] edited this page Nov 17, 2026 · 4 revisions

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


File structure

In the repository

module/                     the installable module
  module.prop               id, name, version
  service.sh                boot entry (BFU/AFU start policy)
  action.sh                 manager Action: (re)launch the daemon
  customize.sh              install-time setup
  uninstall.sh              stop the daemon on removal
  common/
    vddropbear.sh           core library (config, secret store, daemon, argv)
    vddb-webui.sh           WebUI backend (the verbs the page drives)
    config.default          shipped default configuration (documented)
  webroot/
    index.html              the WebUI
    assets/                 logos
  bin/<abi>/                CI-built binaries (not committed)
  META-INF/                 Magisk/KSU installer stub
patches/                    auditable patches vs upstream Dropbear + localoptions.h
scripts/
  build.sh                  build the daemon for all ABIs
  build-bundles.sh          build sftp-server, scp, rsync for all ABIs
docs/                       documentation (this folder) + per-language subdirs
.github/workflows/build.yml CI: build, assemble, track upstream, release
UPSTREAM_VERSION            the pinned upstream Dropbear tag

At runtime (on the device, not in the repo)

/data/adb/vddropbear/
  config                    the live configuration you (or the WebUI) edit
  state/daemon.log          the daemon log
  secret/                   secrets, ONLY when START_IN_BFU=1 (device-encrypted)

/data/misc_ce/0/vddropbear/
  secret/                   secrets by default (credential-encrypted, AFU only)
    hostkey_<type>          the host key
    authorized_keys         public keys
    passwd                  password hashes (PBKDF2)

The runtime config and secrets are intentionally kept when you uninstall, so a reinstall keeps your settings and keys. To wipe them, remove those directories by hand.


This documentation was generated with Claude (Anthropic) and is maintained by VD171. Corrections and improvements are welcome; see CONTRIBUTING.md.

Clone this wiki locally