macgyverd: the on-board crash reporter
Static reading of the 4.7.1 rootfs (firmware/extracted/bebop-2-4.7.1/rootfs). Nothing here touched
the aircraft. Found 2026-10-02 after Ryan spotted the name (“macguyverd”; the real spelling is
macgyverd, after the TV character MacGyver).
Where it lives
Section titled “Where it lives”usr/bin/macgyverd: 32-bit ARM ELF, dynamically linked, 80,948 bytes in Bebop 2 4.7.1. Present in Bebop 2 4.7.1, Bebop 1 4.0.6 and the Skycontroller 3 (mpp3) image bundled in FreeFlight 6 USA. The binaries are NOT byte-identical across products (Bebop 2 vs Bebop 1 sha256 differ); the config file is identical on the two Bebops.etc/macgyver.conf: its config.etc/boxinit.d/90-macgyver.rc: declaresservice macgyverd /usr/bin/macgyverd -f,disabled, plus a one-shotmake_reportservice (/usr/bin/report-generic ${system.report}) started when the propertysystem.reportis set.etc/init.d/rcSline 200:pstart macgyverdafter the eMMC is mounted (comment: “need emmc mounted”). So it is started by rcS even though the boxinit service is marked disabled.
What it collects (from the config and binary strings)
Section titled “What it collects (from the config and binary strings)”Kernel oops (RAM oops / pstore / MTD oops), crash dumps, and Java exceptions and Android ANRs
(presumably shared code from Parrot’s Android-based products; we did not look for a JVM in this rootfs). Reports are compressed
(*.txt.gz names: oops, crashdump, exception, anr), numbered report_NNN, and the build
properties (ro.parrot.build.*), /proc/cmdline and /factory/production_info.xml are read, so a
report can carry product identity.
Config as shipped: max_report_stored = 20; reports folder /data/ftp/internal_000/Debug/crash_reports;
crash dumps in /data/lib/crashdump; Java exceptions in /data/exceptions.
Phoning home
Section titled “Phoning home”auto_send_https_report = 0in the shipped config. Automatic sending is off.- The binary still contains an HTTPS client (libssl 1.0.0), a POST to
/cgi-bin/macgyver/reportcrashon hostcrashreport.parrot.biz, and an embedded certificate it adds to its own trust store. The certificate is self-signed (CA:TRUE), subject O=Parrot Automotive SAS, OU=OS Team, CN=crashreport.parrot.biz, validity 1969-01-01 to 2032-12-31 (the 1969 start date is a zero-epoch artifact, not a real issue date). - It dedupes by SHA-1 (strings
report_compute_sha1,report_db_has_sha1, “doublon filtering”). - Strings also include “non anonymous”, “short backtrace” and “full backtrace” as run modes.
- Public DNS had no record for
crashreport.parrot.bizwhen checked on 2026-10-02 (a plaindig).
Evidence for this unit
Section titled “Evidence for this unit”- First-contact capture: storage reported 0 crash logs (drone state).
Unverified
Section titled “Unverified”- How the “non anonymous” mode is selected, and exactly which fields a sent report would include. Only strings were read; macgyverd was not decompiled or run.
- Whether the reports folder is reachable over the drone’s FTP share the way
network.mdsays (FTP root/data/ftp, from the rf-lab docs, not checked by us). - Whether any Parrot-side server ever answered; the hostname does not resolve now.
Do not publish
Section titled “Do not publish”The embedded certificate’s subject includes an individual Parrot engineer’s email address. Keep it out of the docs site and any public write-up; the organisation and CN above are enough.
Q: Does anything on the drone ever set system.report, and what triggers make_report?
(bin/ardrone3_shell.sh also mentions it; not read yet.)
Comments
Spotted a mistake, or tried this on your own Bebop? Leave a note. Comments are kept on this site's own server.