Skycontroller nap-linux-2.0.0-rc3: services, boot and network exposure
Static read of the Skycontroller
nap-linux-2.0.0-rc3image by one agent, 2026-10-04. Status: Agent-cited, with these claims re-checked by the commissioning session against the files: the two inetd FTP lines (ports 21 and 51, root,-wS), the NAT script (three DNAT rules to the drone’s FTP ports plus masquerade, no filter rule in that script),ro.debuggable=1andservice.adb.tcp.port=9050inetc/default.nap.propwithro.adb.secureabsent frometc/(positive control: the same search finds the port property), the adbd service entry having no user line, the AP radio settings, and that busybox contains an “Anonymous FTP server” applet. Not re-derived: the service table, boot-stage order, factory reader properties, and everything marked Inference. This describes what the image configures, not what any unit does at runtime. No device was contacted. Whether a given Skycontroller 2 runs this image is unestablished (see the identity reports).The exposure section describes unauthenticated services as configured in the firmware image. It has not been checked against a live unit.
Static analysis only. Image root: firmware/extracted/skycontroller-nap/rootfs. Paths below are relative to it. Tags: Verified (file or bytes read), Agent-cited, Inference, Open. Every negative result was checked by running the same /usr/bin/grep search on a string known to exist (positive control) before being trusted.
Summary
Section titled “Summary”- Boot is boxinit (
sbin/boxinit) readingetc/boxinit.rc, which importsboxinit.dragonbase.rc, which imports the 16 files inetc/boxinit.d/. They declare 19 services across classes core, main, mpp and one unclassed console. Verified. etc/default.nap.prop:2-3setsro.debuggable=1andservice.adb.tcp.port=9050. That property starts a root console on the UART, adbd, and ulogcatd (etc/boxinit.rc:14,50-adb.rc:2,90-ulogcat.rc:11). Verified.- inetd (
etc/inetd.conf:1-2) serves two BusyBox anonymous FTP servers as root: port 21 rooted at/data/lib/ftpand port 51 rooted at/data/lib/update_ftp, both with upload enabled (-w) and directories created mode 0777. No authentication option is present. Verified. - Drone link:
wifidSTA onwlan0(qca9375) joins the drone at static fallback 192.168.42.3. Phone-facing AP:wifid-aponwlan1(wl18xx) at 192.168.44.1, WPA2-PSK, DHCP 192.168.44.10 to .100 from dnsmasq, with the DHCP server’s DNS disabled (port=0). Verified (config and strings); the key’s source is Open. start_dnsmasq_wlan1enables IP forwarding and DNATs controller ports 121, 151, 161 to the drone’s FTP ports 21, 51, 61 overwlan0, with MASQUERADE. There is no filter table rule anywhere in the image. Verified.- Updates:
ro.updater.filename=nap_update.plf, watch dir/data/lib/update_ftp(the port-51 FTP root), USB updates not copied to/update. The consumer of those properties isusr/bin/mppd. Verified for the properties; the verification done on a dropped file is Open. - Factory data is read once at
early-bootbynap_factory_readerfrom/factory/parameters.xml,/customer_prod/parameters.xml,countrylock.txtandtype.txtintoro.factory.*properties.ro.factory.typeselectsetc/mppd/<type>/(bebopormilosexist). Verified. - A person who joins the controller’s AP with the Wi-Fi key can, from the image alone, reach unauthenticated writable FTP as root on 21 and 51, and (if
ro.debuggable=1holds at runtime) adbd on tcp 9050. Verified as configuration; runtime state is Inference.
Boot stages
Section titled “Boot stages”sbin/boxinit strings contain, in this order: early-init, keychord_init, early-fs, post-fs, post-fs-data, property_service_init, signal_init, check_startup, early-boot, early-boot-main, queue_property_triggers (Verified, byte order in the binary). The stages init, fs, boot and boot-main are shorter or generic strings and were not located in that run; their position between the others is Inference from the names and from how the rc files use them. The Bebop 2 page lists the same stage set (docs-site/src/content/docs/reference/boxinit-services.md:259).
Likely order (Inference): early-init, init, early-fs, fs, post-fs, post-fs-data, early-boot, early-boot-main, boot, boot-main, then on property: triggers as properties change.
| Stage | Action | File:line | Status |
|---|---|---|---|
| early-init | export PATH, BOXINIT_DATA=/data, TERM, TMPDIR/TMP/TEMP=/tmp, HOME=/data/home/root | etc/boxinit.dragonbase.rc:6-15 |
Verified |
| init | export TERM; loglevel 5; printk 1; mount debugfs; overcommit_memory 1, ratio 90; /proc/cpu/alignment 5; panic_on_oops 0; modprobe path; wmem_max 1 MB |
etc/boxinit.rc:44-66 |
Verified |
| init | write "ulog_kmsgd 17" to /sys/devices/virtual/misc/ulog_main/logs |
etc/boxinit.d/90-kmsgd.rc:2-3 |
Verified |
| init | clear /proc/sys/kernel/hotplug (udevd takes over) |
30-udev.rc:26-27 |
Verified |
| early-fs | mkdir /dev/shm; mount tmpfs on shm and /tmp; create /tmp/{cache,lock,run,tmp,log,etc}; empty /tmp/etc/resolv.conf |
etc/boxinit.dragonbase.rc:23-34 |
Verified |
| fs | mount ubifs ubi1:factory on /factory ro, ubi2:customer_prod on /customer_prod ro, ubi0:data on /data rw, ubi0:cache on /update rw (all nosuid nodev) |
etc/boxinit.rc:69-72 |
Verified |
| fs | if /data/.layout_version exists: factory_reset android |
etc/boxinit.rc:76 |
Verified |
| fs | if /update/.factory_reset exists: run factory_reset, then delete the flag file |
etc/boxinit.rc:78-79 |
Verified |
| post-fs | mkdir /tmp/avahi, /tmp/avahi/services (etc/avahi/services is a symlink to it) |
50-avabye.rc:1-3 |
Verified |
| post-fs-data | mkdir /data/property 0700, /data/lib 0755 system, /data/home, /data/home/root |
boxinit.dragonbase.rc:17-21 |
Verified |
| post-fs-data | mkdir /data/lib 0777, /data/lib/ftp 0777, /data/lib/update_ftp 0777, /data/lib/misc 0777; set persist.periodic.log=1, persist.wifi.periodic.log=1 |
boxinit.rc:83-90 |
Verified |
| post-fs-data | mkdir /var/lib/crashdump |
30-crashdump.rc:1-2 |
Verified |
| early-boot | statexec /factory/parameters.xml /usr/bin/nap_factory_reader (runs only if that file exists) |
boxinit.rc:18 |
Verified |
| early-boot | set ro.product.model=Skycontroller, ro.product.model.id=0x0913, updater properties, USB product, pid 6860, sensor names; persist.product.name from ro.factory.default.ssid (-z: only if empty) |
boxinit.rc:21-41 |
Verified |
| early-boot-main | wait for /dev/.udev_perms_done |
30-udev.rc:30-31 |
Verified |
| boot | ifup lo, hostname nap, domainname localdomain, class_start core |
boxinit.rc:94-99 |
Verified |
| boot | rw.debuggable from persist.debuggable, then ro.debuggable, then ro.boot.debuggable (-z fallbacks). Only in boxinit.base.rc, which nothing imports in this image (see open questions) |
boxinit.base.rc:8-11 |
Verified (file); not imported: Inference |
| boot-main | class_start main; write USB gadget values and enable android_usb with function adb, VID 19cf |
boxinit.rc:103, 50-adb.rc:10-19 |
Verified |
| property | ro.debuggable=1: start console, adbd, ulogcatd |
boxinit.rc:14-15, 50-adb.rc:2-3, 90-ulogcat.rc:11-12 |
Verified |
| property | mpp.services.start=1: class_start mpp (set by usr/bin/bottom_board_update via sprop) |
boxinit.rc:105-107 |
Verified |
| property | gps.socket.ready=1: insmod the wl18xx module set, start wifid-ap; =0: stop wifid-ap (property set by btgpsdemux) |
50-wifi.rc:25-37 |
Verified |
Properties are loaded by boxinit from /etc/default.prop, /etc/default.%s.prop and /etc/build.prop (strings in sbin/boxinit, Verified). With ro.hardware = nap the second is etc/default.nap.prop, the only default file present (hardware name is Inference; the file name and ro.build.alchemy.product=nap agree). Persistent properties live in /data/property (persist.*).
Service table
Section titled “Service table”19 services in 16 files, plus console in boxinit.rc. Columns follow the Bebop 2 page. - means the keyword is absent; when user is absent boxinit’s default is Inference (root, as the Bebop 2 page treats it; not confirmed here).
| File | Service | Command line as written | Class | User | Group | Flags | Capability, setenv, socket | Trigger | Status |
|---|---|---|---|---|---|---|---|---|---|
boxinit.rc:6-11 |
console | /usr/bin/askfirst /bin/sh -l |
core | root | log | console, disabled | - | ro.debuggable=1 |
Verified |
30-crashdump.rc |
crashdumpd | /usr/bin/crashdump -d |
main | root | - | - | capability SYS_PTRACE | class main | Verified |
30-udev.rc |
udevd | /usr/bin/ulogwrapper /usr/bin/udevd |
core | root | inet | - | - | class core | Verified |
40-jubamountd.rc |
jubamountd | /usr/bin/jubamountd |
core | root | - | - | capability SYS_ADMIN SETGID | class core | Verified |
50-adb.rc |
adbd | /usr/bin/adbd |
core | - | - | disabled | socket adbd stream 660 0 0 |
ro.debuggable=1 |
Verified |
50-avabye.rc |
avabye | /usr/bin/avabye |
main | root | - | - | - | class main | Verified |
50-btgpsdemux.rc |
btgpsdemux | /usr/bin/btgpsdemux |
main | - | - | - | - | class main | Verified |
50-wifi.rc |
wifid | /usr/bin/wifid --mode STA --ip 192.168.42.3 --dhclient |
main | root | - | - | setenv WIFID_DRIVER cfg80211driver, CHIP qca9375, module paths | class main | Verified |
50-wifi.rc |
wifid-ap | /usr/bin/wifid --mode AP --ip 192.168.44.1 --suffix ap |
main | root | - | disabled | setenv CHIP wl18xx | gps.socket.ready=1 |
Verified |
50-wifi.rc |
wifid-dhclient | /usr/bin/ulogwrapper /sbin/udhcpc -S -f -q -n -A10 |
main | root | - | disabled, oneshot | - | started by wifid (ctl.start, string @wifid-dhclient) |
Verified (rc); starter Verified by strings |
60-gpsd.rc |
gpsd | /usr/bin/gpsd |
main | - | - | - | - | class main | Verified |
60-inetd.rc |
inetd | /usr/bin/ulogwrapper /usr/sbin/inetd -f |
main | root | root | - | - | class main | Verified |
60-sensorsd-mpp.rc |
sensorsd-mpp | /usr/bin/sensorsd-mpp |
main | root | - | - | - | class main | Verified |
90-aoad.rc |
aoad | /usr/bin/aoad |
mpp | root | - | - | - | mpp.services.start=1 |
Verified |
90-kmsgd.rc |
kmsgd | /usr/bin/kmsgd |
main | root | - | - | capability SYSLOG; setenv ULOG_DEVICE kmsgd | class main | Verified |
90-ulogcatd.rc |
ulogcatd | /usr/bin/ulogcat -F /etc/ulogcatd.conf |
main | root | log inet | disabled | capability SYSLOG | ro.debuggable=1 |
Verified |
99-dnsmasq.rc |
dnsmasq_wlan1 | /usr/bin/ulogwrapper /usr/bin/start_dnsmasq_wlan1 |
main | root | - | disabled, oneshot | - | wifid (dnsmasq_%s with ctl.start/ctl.restart, strings) |
Verified (rc); starter Verified by strings |
99-hudd.rc |
hudd | /usr/bin/hudd -platform eglfs |
mpp | root | - | disabled | - | none found in rc files; Open | Verified (rc) |
99-mppd.rc |
mppd | /usr/bin/mppd |
mpp | root | - | - | - | mpp.services.start=1 |
Verified |
Notes. class_start skips disabled services, so wifid-ap, wifid-dhclient, dnsmasq_wlan1, hudd, adbd, ulogcatd and console start only through their triggers. The console service is class core and disabled; every service has a class line. Every service in boxinit.d that has a user line says root. None of the rc files use user system or any other unprivileged user for network-facing daemons. The nap image has no shpoison, ptpd, arducopter or ledd services (those are Bebop 2 only).
Network and ports
Section titled “Network and ports”Interfaces (Verified): wlan0 is the STA toward the drone (wifid with qca9375, static fallback 192.168.42.3, DHCP client by udhcpc -A10; the DNAT target 192.168.42.1 matches the drone). wlan1 is the AP the phone joins (wifid-ap, wl18xx, 192.168.44.1; etc/avabye.conf:4 names wlan1,eth*,usb*; start_dnsmasq_wlan1 names wlan0 as the outbound interface). USB gadget presents adb (VID 19cf, PID 6860) (boxinit.rc:32, 50-adb.rc:16-18).
AP radio (Verified): etc/libshsettings/wifi-ap.cfg:2-8: country US, outdoor true, autoselect=false, band=4, channel=6. STA profile wifi.cfg: autoselect true, channel -1. The band number meaning is Open. Hostapd options generated by usr/lib/wifid/cfg80211driver.so (strings): ctrl_interface, ssid, country_code, wpa=2, wpa_key_mgmt=WPA-PSK, wpa_passphrase, hw_mode=g or a, ieee80211d/h/n=1, written to /tmp/hostapd.conf. So the AP security type is WPA2-PSK and a passphrase exists, set at runtime from settings under /var/lib/libshsettings (that is /data/lib/libshsettings). No passphrase is stored in any file I read in etc/. The generator has no open-network branch among the strings found (Inference for “no open mode”; the strings none exists but its use was not traced).
etc/hostapd.conf (lines 1-7: driver=nl80211, auth_algs=1, beacon 100, dtim 2, max_num_sta=200, rts 2347, fragm 2346) has no ssid, channel or wpa lines. A search for the path /etc/hostapd.conf in usr, bin, sbin, lib found nothing, while the same search for /etc/dnsmasq.conf found two hits (positive control), so nothing in the image names it (Verified). It is a stock template; wifid uses /tmp/hostapd.conf instead (Inference that it is unused).
DHCP (Verified): etc/dnsmasq.conf:1-6: port=0 (DNS service off), dhcp-authoritative, leases at /var/lib/misc/dnsmasq.leases, bind-interfaces, dhcp-range=192.168.44.10,192.168.44.100,infinite. Note bind-interfaces with no interface= line; which interface it binds to is decided at runtime (Open).
mDNS (Verified): avabye (etc/avabye.conf): INTERFACE=wlan1,eth*,usb*, SERVICE_DIR=/etc/avahi/services (symlink to /tmp/avahi/services). Binary strings show it answers DNS-SD queries (_services._dns-sd._udp.local) and announces service files it finds there by inotify, as JSON-carrying records (addr %s port %d json '%s'). The service files are written at runtime by arsdk in mppd (arsdk_publisher_avahi_new), so the exact advertised service type string is not in the image text I read (Open; arsdk service type, _arsdk-<productid>._udp, is Agent-cited from the ARSDK convention and not found as a literal here).
inetd (Verified, etc/inetd.conf):
| Line | Port | Handler | Root dir | Notes |
|---|---|---|---|---|
| 1 | tcp 21 | ftpd -wS /var/lib/ftp |
/data/lib/ftp |
root, upload allowed, syslog |
| 2 | tcp 51 | ftpd -wS /var/lib/update_ftp |
/data/lib/update_ftp |
root, upload allowed, syslog |
BusyBox is v1.25.0 (bin/busybox strings). Its usage text calls this an anonymous FTP server, with -w allow upload, -S log to syslog, and DIR as the new root. No -a or user-database option is accepted in that help text, and no /etc/shadow exists (Verified). So the ftpd runs as root, chrooted to the directory argument, with no login check (Inference for the no-login behaviour from the usage text and flags; the code path was not disassembled). Directory mode is 0777 (boxinit.rc:84-85). The ftp user in etc/passwd:11 is not used by the inetd line (Verified: nowait root).
adbd (Verified): etc/default.nap.prop:3 service.adb.tcp.port=9050; usr/bin/adbd contains the strings service.adb.tcp.port, persist.adb.tcp.port, ro.adb.secure, service.adb.root. ro.adb.secure appears only in the adbd binary; a search of etc/ for it returns nothing, and the same search for service.adb.tcp.port returns default.nap.prop (positive control). So adb authentication is not enabled by any file in the image (Verified for files; the adbd default when the property is unset is Inference: not secure). adbd has no user line in its service block. Listening on tcp 9050 when ro.debuggable=1 is Inference (property and service present; no running system observed). USB adb is enabled in boot-main regardless of the TCP port (the gadget write is not conditional; the adbd service is).
Debug console (Verified): the console service runs askfirst /bin/sh -l as root on the boot console (ro.boot.console=ttyPA3, default.nap.prop:1) when ro.debuggable=1. askfirst prints “Press Enter to start” then spawns the shell with no password (strings; Inference for no password since the shell is exec’d directly).
Other listeners and sockets (binary strings, so Inference for runtime behaviour):
| Component | What the strings show | Status |
|---|---|---|
mppd |
arsdk_backend_net_start_listen, arsdk_backend_mux_start_listen, pomp_ctx_listen. The TCP port number is not a literal in the binary (a 4 or 5 digit literal search found none). The ARSDK discovery/control port is Agent-cited from the Bebop 2 side as 44444 and not confirmed here |
Verified (symbols); port Open |
ulogcat |
-p <port> serves logs on TCP; the line is commented out in etc/ulogcatd.conf:10. Local control socket @/com/parrot/ulogcat/<addr>, commented (-P control -R, line 27) |
Verified: not enabled |
crashdump |
abstract unix socket @crashdump |
Verified (strings) |
wifid |
@wifid, @wifid-<suffix> abstract sockets (pomp), @wifid-dhclient |
Verified (strings) |
sensorsd-mpp, gpsd, btgpsdemux |
@sensorsd, @gps, /tmp/gps.socket (unix, local) |
Verified (strings) |
jubamountd |
@/org/parrot/jubamountd |
Verified (strings) |
busybox telnetd, ntpd, httpd |
telnetd and ntpd applets are compiled into busybox; httpd and tftpd and sshd are not. No rc file or inetd line starts telnetd or ntpd. A search of etc for telnetd found nothing, and the same search for ftpd found inetd.conf |
Verified: not started |
iptables (Verified): the binary exists (usr/sbin/iptables -> xtables-multi). The only invocations are in usr/bin/start_dnsmasq_wlan1:17-20, all in the nat table: POSTROUTING -o wlan0 MASQUERADE and three PREROUTING DNATs, tcp 121 to 192.168.42.1:21, tcp 151 to :51, tcp 161 to :61. It also sets ip_forward=1 and loads nf_conntrack_ftp for ports 21, 51, 61 and nf_nat_ftp. No filter table rule, no INPUT rule, no ip6tables use anywhere in etc/ or the shell scripts I found (search of etc and usr/bin/* text for iptables returned only this script and the binaries). So default policy is accept (Inference from absence; policy set from outside the image is Open).
Update path
Section titled “Update path”| Item | Where | Status |
|---|---|---|
| File name | setprop ro.updater.filename "nap_update.plf" (boxinit.rc:25) |
Verified |
| USB updates | ro.updater.usb.nocopy 1: not copied to /update (boxinit.rc:26) |
Verified |
| FTP watch dir | ro.updater.watch.dir /data/lib/update_ftp (boxinit.rc:28); the same directory is the root of the port-51 ftpd (inetd.conf:2) and is created 0777 (boxinit.rc:85) |
Verified |
| Consumer of the properties | usr/bin/mppd has the strings ro.updater.filename, ro.updater.watch.dir, ro.updater.usb.nocopy; usr/lib/libarsdk.so has the arsdk updater and ftp interfaces (arsdk_updater_itf_create_req_upload, arsdk_updater_read_fw_info, arsdk_updater_md5_to_str, arsdk_updater_cmp_fw_version) |
Verified (strings) |
| Drone updates | controller forwards ports 151 to the drone’s 51 (start_dnsmasq_wlan1:7,19), the drone’s update FTP port; an update pushed to the controller’s port 151 reaches the drone |
Verified (script); purpose Inference |
| Update validation | md5 and fw version compare functions exist in libarsdk. Whether mppd verifies a signature on a plf dropped into the watch dir is Open |
|
| Partition | ubi0:cache is mounted at /update rw (boxinit.rc:72); a file /update/.factory_reset triggers a wipe at next boot (boxinit.rc:78-79) |
Verified |
| Logging written to the update partition | -f /update/log, rotation 16 MB x2 (etc/ulogcatd.conf:17,21) |
Verified |
| Bottom board | usr/bin/bottom_board_update flashes lib/firmware/xmega.hex and sets mpp.services.start=1 |
Verified (strings) |
The dropped-file path is therefore: anonymous FTP upload to port 51 (or to 151 on the controller’s own side) lands in /data/lib/update_ftp, where mppd watches for nap_update.plf (Inference for the watch-and-apply behaviour: the properties and the directory match, the code was not read).
Factory and persistence
Section titled “Factory and persistence”Correction applied 2026-10-04: this agent report had the serial and MAC sources the wrong way round; the software-stack agent read them the other way and the string order in usr/bin/nap_factory_reader (serial_number, /customer_prod/parameters.xml, then mac_address, /factory/parameters.xml) agrees with the second reading. Inference from string order, not disassembled; the early-boot statexec still tests only for /factory/parameters.xml.
nap_factory_reader (Verified, usr/bin/nap_factory_reader strings; invoked at boxinit.rc:18 with statexec, so it runs only if /factory/parameters.xml exists):
| Source | Property set |
|---|---|
/customer_prod/parameters.xml (key serial_number) |
ro.factory.serial |
/factory/parameters.xml (key mac_address) |
ro.factory.wifi-ap.mac_address (and the ro.factory.wifi%s%s.mac_address pattern wifid reads) |
/customer_prod/countrylock.txt |
ro.factory.country_lock |
/customer_prod/type.txt (error string “Unable to read type file”) |
ro.factory.type |
| derived | ro.factory.default.ssid, then persist.product.name copies it if unset (boxinit.rc:35) |
The /factory and /customer_prod directories in the extracted image are empty mount points; their contents live in separate UBI volumes not in this rootfs (Verified: directories empty). Values are Open.
ro.factory.type: mppd builds the path /etc/mppd/{ro.factory.type} (string in usr/bin/mppd), and libmppd_hw_nap.so also reads it. The image has etc/mppd/bebop/ and etc/mppd/milos/, each with mapping files for anafi4k, bebop_2, bebop, chimera, disco. So the type selects which button and stick mapping set loads (Verified for the path and directories; which type a unit has is Open). ro.factory.js.centers and ro.factory.js.min_max are read by mppd (joystick calibration, strings); where they are set is Open (not in nap_factory_reader’s strings).
factory_reset (Verified, usr/bin/factory_reset, 138 bytes): rm -rf /data/* and /data/.*; with argument android also rm -rf /update/* and /update/.*. Triggered at fs by /update/.factory_reset (any content) or, for the android variant, by the presence of /data/.layout_version. Because /update is on a writable partition and /data/lib/update_ftp is writable by FTP, whether a remote party can plant .factory_reset depends on what /update exposes, which is not reachable from either FTP root (/data/lib/ftp, /data/lib/update_ftp), so Inference: no, not through FTP.
customer_prod: mounted read-only (boxinit.rc:70), holds the per-unit data above. Mount flags for all four UBI volumes: no_chk_data_crc nosuid nodev; factory and customer_prod are ro.
jubamountd (etc/jubamountd.conf, Verified): lines 31 and 34 are the only live rules. sd* vfat auto utf8,uid=1000,gid=1000,fmask=702,dmask=702,shortname=mixed and sd* ntfs auto nls=utf8,uid=1000,gid=1000,umask=702. Mounts under the default /tmp/.mnt (no MOUNTPATH given). fmask and dmask are masks of bits removed (vfat semantics, as umask), so 702 removes all owner bits and other-write: on files the result is group rw, others read (064), on directories group rwx, others rx (075), with uid/gid 1000. The owner (system) therefore has no access bits of its own on a stick, which looks odd and is Open (Inference that this is intentional so a group-based reader works). Daemon runs as root with SYS_ADMIN and SETGID.
udev_perms (etc/udev_perms.conf:15-20, Verified): input 0660 root:input, snd 0660 root:audio, usb bus 0660 root:usb, tty 0660 root:tty, and /dev/ulog_* 0666 root:log. The log devices are world-readable and writable by mode, though the comment on line 19 says only group log can read the full logs (the comment and the mode disagree; Inference that another rule or the driver restricts it). udev trigger arguments (etc/udev_trigger_args.conf) replay add events for block, firmware, hidraw, input, mmc, net, tty, usb, switch.
Persistence (Verified): /data is rw UBIFS and holds property/ (persist.* properties), lib/ (/var/lib is a symlink to /data/lib), home/root, and lib/libshsettings (Wi-Fi settings). /tmp is tmpfs and holds hostapd.conf, avahi service files, the GPS socket.
Logging (Verified): kmsgd (class main, root, SYSLOG) reads the kernel log via klogctl into ulog (ulog_kmsgd, buffer 17). ulogcatd (debug only) runs ulogcat -v long -lku -f /update/log -r 16384 -n 1 (etc/ulogcatd.conf:7,17,21), kernel and ulog messages to a rotating file in /update. crashdump -d runs as root with SYS_PTRACE, listens on abstract socket @crashdump, writes reports to /var/lib/crashdump (/data/lib/crashdump) as crash_NN directories, and reads ro.hardening.level (set by nothing in etc/, Verified by search). persist.periodic.log and persist.wifi.periodic.log are set to 1.
Exposure
Section titled “Exposure”What a person on the controller’s network could reach, from the image alone. “Network” here means a client on the controller’s AP (wlan1, 192.168.44.0/24), a host on the drone-side STA link, or a USB host. Descriptive only.
| # | Claim | Status |
|---|---|---|
| 1 | To join the AP a client needs the WPA2-PSK key. A passphrase mechanism exists (wpa=2, WPA-PSK, wpa_passphrase generated into /tmp/hostapd.conf). Its default value or derivation is not in any file I read |
Verified (mechanism); key source Open |
| 2 | Once on the AP, the client gets a lease from dnsmasq (192.168.44.10 to .100, infinite lease) and has no DNS service on the controller (port=0) |
Verified |
| 3 | Controller tcp 21: anonymous-style FTP as root chrooted to /data/lib/ftp, upload allowed, directory mode 0777, no login option configured |
Verified (config); no-login Inference |
| 4 | Controller tcp 51: same, rooted at /data/lib/update_ftp, the directory mppd watches for update files. Uploading nap_update.plf there is the documented update route |
Verified (config); apply behaviour Inference |
| 5 | Controller tcp 121, 151, 161 forward to the drone’s 21, 51, 61 (media, update, flight-plan FTP), so a client on the controller AP can reach the drone’s FTP services through the controller, with the source masqueraded as the controller. This requires the STA link to be up | Verified (rules); runtime Inference |
| 6 | tcp 9050 adbd, if the property is honored and the service started. ro.debuggable=1 is shipped in the image and ro.adb.secure is set nowhere. A TCP adb session as the adbd user (no user line, so root by boxinit default) would be unauthenticated |
Verified (files); runtime Inference |
| 7 | USB: adb gadget function enabled at boot-main (VID 19cf, PID 6860). The phone link uses aoad (Android Open Accessory) and the ARSDK mux backend, both class mpp |
Verified |
| 8 | ARSDK control over mppd’s net backend, discovered via avabye mDNS on wlan1, eth* and usb*. Port and any pairing step are not in the files read |
Verified (symbols); port Open |
| 9 | UART console: root shell on ttyPA3 via askfirst when ro.debuggable=1; needs physical access, not network |
Verified |
| 10 | Not exposed by configuration: ulogcat TCP log port (line commented out), telnetd, ntpd server, sshd (not present), a filter firewall (none present, so no host firewall limits items 3 to 6) | Verified (absence, checked with positive controls) |
| 11 | Every network-facing daemon found (inetd, ftpd instances, wifid, mppd, avabye, adbd) is declared with user root or no user. No privilege drop appears in the rc files |
Verified (rc); runtime Inference |
| 12 | /dev/ulog_* are mode 0666 per udev_perms.conf:20, so any local process can write to and read the log devices; not reachable from the network |
Verified (file) |
Addendum 2026-10-04: are the services behind the AP’s key? (checked in the image, plus one live reading)
Section titled “Addendum 2026-10-04: are the services behind the AP’s key? (checked in the image, plus one live reading)”The exposure table above says a client needs the controller AP’s WPA2 key. That is not the whole picture, because in this pairing the controller is also a client (STA, wlan0) on the drone’s Wi-Fi, which the notes record as an open network on the Bebop 2. Checked: the two inetd.conf lines carry no address prefix, so BusyBox inetd binds them to all interfaces (Verified for the config, standard inetd behaviour for the binding). usr/bin/adbd imports socket_inaddr_any_server, the wildcard-listener helper, and has a tcp:%d listener and a gListenAll flag; that its 9050 listener uses the wildcard helper is Inference (the call path was not traced, and the default of gListenAll is Open). No filter-table rule exists anywhere in the image (the only iptables lines are NAT in start_dnsmasq_wlan1), so nothing in the image restricts which interface reaches them. One live reading agrees in direction: the skycontroller2 session reached adb on 9050 and FTP on 21 of a live Skycontroller 2 over a USB-network interface, not over the AP (relayed, one unit). So these services are not AP-only on that unit, and the earlier wording “behind a credential” is withdrawn. What follows for the drone-side network (services reachable from the open Wi-Fi the controller joins) is a consequence of wildcard binding plus an address on that network: plausible, not observed, and it is the NG build, not the unit’s own mpp build. A ping sweep of the drone’s AP by the other session, made at a time when the controller’s pairing state is unknown, found no controller; that is inconclusive.
Not examined
Section titled “Not examined”Disassembly of mppd, wifid, adbd, libarsdk.so and busybox ftpd (only strings, symbols and config text). The kernel image and modules (no netfilter or sysctl hardening review). The /factory, /customer_prod, /data and /update volume contents (not in the rootfs). Qt and HUD assets. The other Wi-Fi drivers (ath6k, qcacld). etc/mppd/*/mapping_*.cfg button maps. libshsettings key schema for the AP security and passphrase. How ro.hardware resolves at runtime. Nothing was run and no device was contacted.
Open questions
Section titled “Open questions”- Where does the AP WPA2 passphrase come from on a fresh unit (factory file, derived from serial or SSID, user setting)? Not in
etc/; likely in thelibshsettingsstore or a factory parameter, not read here. - What TCP port does
mppd’s ARSDK net backend listen on, and what is the advertised mDNS service type? No literal found; arsdk writes the avahi file at runtime. - Does
mppdverify a signature or only md5/version on anap_update.plfdropped into/data/lib/update_ftpor arriving by USB? - Does the busybox 1.25.0
ftpdas built accept any login without credentials (disassemblehandle_user/handle_pass), and does the chroot cover the symlink/var/lib? - Is
ro.debuggable=1overridden at runtime by a persistent property or kernel cmdline (ro.boot.debuggable)?boxinit.base.rccomputesrw.debuggable, but nothing in this image importsboxinit.base.rc, and the triggers usero.debuggable, notrw.debuggable. - What starts
hudd? It isdisabledin class mpp, and no rc trigger starts it; likelymppdor the HUD manager viactl.start(strings not checked). - Does
dnsmasqbind-interfaceswith nointerface=line bind only wlan1? The script gives no-i/--interfaceoption. - The
/dev/ulog_*mode 0666 versus the “group log only” comment inudev_perms.conf. - Meaning of
band=4andchannel=6inwifi-ap.cfgfor the wl18xx (2.4 GHz channel 6 is the natural reading; not confirmed).
Comments
Spotted a mistake, or tried this on your own Bebop? Leave a note. Comments are kept on this site's own server.