opendrop: an AirDrop implementation gated on AWDL, libarchive, and macOS keys
An open Apple AirDrop implementation written in Python
At a glance
- What is it?
- OpenDrop speaks Apple AirDrop's protocol from the command line, so it can share files with iOS and macOS devices. Its costs are strict platform prerequisites, an experimental disclaimer, and no authentication of the peer on the other end.
- Who is it for?
- Use opendrop if you need to hand files to iOS or macOS devices from Linux, you accept the AWDL dependency, and you treat every received file as untrusted. Do not use it as a shipping channel for sensitive material: no peer authentication is performed, received files are accepted without a connection state, and only one file can be sent at a time.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 90 days ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- seemoo-lab/opendrop9,954 ★ · +209
| Repository | 2026-09-22 | 2026-11-15 |
|---|---|---|
| seemoo-lab/opendrop | 9.7k | 10k |
209 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
AWDL is the gate: macOS, or Linux running OWL
AirDrop runs exclusively over Apple Wireless Direct Link, and OpenDrop's compatibility claim inherits that restriction exactly. To be protocol-compatible, the target platform has to support that specific Wi-Fi link layer, which in practice means one of two setups: macOS, where the interface exists, or a Linux system running an open re-implementation such as OWL from the same lab. The project's own requirement statement puts it plainly, and there is no Windows path in it at all. That is the first thing to check before anything else, because the remaining instructions are worthless on a machine whose Wi-Fi stack cannot speak AWDL.Also, on Linux the discovery and link layers come from a separate project you have to install and keep working alongside this one.
Contacts-only receivers need credentials extracted from a macOS keychain
The most restrictive limit was written down, crossed out, and replaced. The struck-through line said that OpenDrop only supported sending to Apple devices discoverable by everybody, because the default contacts only mode requires Apple-signed certificates. What replaced it is a workaround rather than a reimplementation: contacts-only devices are supported by using extracted AirDrop credentials, meaning keys and certificates taken from macOS through the lab's keychain extractor, published as a separate project called airdrop-keychain-extractor. The consequence for a reader is precise about who is left out. If your only machine is Linux, you can send to everybody-mode receivers, and to reach a contacts-only device you still need those credentials, which come from a Mac. The extraction tool is separate software with its own risk profile, and OpenDrop itself does not generate them.
pip3 install opendrop is easy; a current libarchive on macOS is the real prerequisite
Installing the published package is one line, and the development version is two:
pip3 install opendropgit clone https://github.com/seemoo-lab/opendrop.git
pip3 install ./opendropThe dependency that actually bites is libarchive, which has to be a current version. Linux distributions ship up-to-date builds, so on Linux this is usually a non-event. macOS ships a rather old version, and the fix is to install a newer one, for example through Homebrew:
brew install libarchiveOpenDrop sets DYLD_LIBRARY_PATH itself to look for the Homebrew version, which is why the common case works without configuration. If you install the library any other way, that automatic path is wrong and you have to update the variable yourself. Python 3.6 or later is required, and setup.py still advertises only interpreters up to 3.9 in its classifiers while declaring python_requires of 3.6 or later.
find lists receivers with an index, an ID and a name, resolved in that order
Sending is a two-step procedure. First you discover what is nearby, and stop the process once you see the device you want:
$ opendrop find
Looking for receivers. Press Ctrl+C to stop ...
Found index 0 ID eccb2f2dcfe7 name John's iPhone
Found index 1 ID e63138ac6ba8 name Jane's MacBook ProThen you send, addressing the receiver by that index:
$ opendrop send -r 0 -f /path/to/some/file
Asking receiver to accept ...
Receiver accepted
Uploading file ...
Uploading has been successfulYou can pass the ID or the name instead, because the argument is interpreted as an index first, an ID second and a name third, and the command fails when nothing matches. Indexes are also positional in a list that changes as devices come and go, so a name or ID is the safer key. Sending a web link, added in v0.13, makes the receiving device open its browser on accept.
receive accepts everything, automatically, into the current directory
The receive side is one command:
$ opendrop receiveThat is the entire interface. OpenDrop accepts all incoming files automatically and puts what it receives in the current directory, so where you run the command decides where files land. There is no prompt and no confirmation step, and the project states plainly that this happens because the connection state is missing. Read that together the security limitations and the picture is uncomfortable: any device that can reach you over AWDL can place a file in your working directory without asking, and there is nothing in this command to change that. The same asymmetry applies in the other direction. Link sending exists since v0.13, but receivers still only support receiving regular files, so a link sent to an OpenDrop receiver is not a supported path.
No peer authentication, and Apple's root certificate is never verified
The limitations section is the most useful part of the documentation, because it is explicit about what the tool does not do. There is no peer authentication as in Apple's AirDrop. Specifically, OpenDrop does not verify that the TLS certificate is signed by Apple's root, and does not verify that the Apple ID validation record is correct, even though the root certificate is shipped inside the package as opendrop/certs/apple_root_ca.pem. Combined with automatic acceptance of received files, that means the receiving side cannot tell you who sent what. Discovery is also incomplete: Apple devices only start their AWDL interface and AirDrop server after a custom Bluetooth Low Energy advertisement, so an AirDrop receiver may stay invisible even when it is set to be discoverable by everybody. On multi-file transfers the gap is functional: AirDrop sends several files at once and OpenDrop does not, since it would require adding more files to the archive and modifying the HTTP request that asks the receiver.
v0.13.0 dates from 2021 while the last push is 2026-08-17
Two dates matter more than any feature line. The newest published release is v0.13.0 from 2021-04-29, preceded by v0.12.3 in 2020-12 and v0.12.2 in 2020-12, while the last push to the default branch master was 2026-08-17. The newest release is therefore about five years old, while the repository has had pushes since. The project also asks readers to read it as research output: it is experimental software produced by reverse engineering, does not support all features of AirDrop, may be incompatible with future AirDrop versions, and is not affiliated with or endorsed by Apple. The stated homepage is disclaimed as no longer associated with the project. The repository also carries tooling: a Makefile driving isort, black in check mode, flake8, pylint with a setup.cfg rules file and pytest, plus CITATION.cff, requirements-dev.txt and a tests/ directory. The author says plainly that they lack the capacity to work on the listed TODOs.
Editorial conclusion
Use opendrop if you need to hand files to iOS or macOS devices from Linux, you accept the AWDL dependency, and you treat every received file as untrusted. Do not use it as a shipping channel for sensitive material: no peer authentication is performed, received files are accepted without a connection state, and only one file can be sent at a time. Before installing, check that you can supply a current libarchive on macOS, and note that the newest published release is v0.13.0 from 2021-04-29 even though the last push was 2026-08-17, so the newest tagged release is about five years old.
Frequently asked questions
How do you send a file with opendrop on the command line?
Run opendrop find to list nearby receivers with an index, an ID and a name, then use opendrop send with the receiver and a file path. The receiver argument is interpreted as an index first, an ID second and a name third, and the command fails if no match is found.
What is opendrop used for?
It is a command-line tool for sharing files directly over Wi-Fi, protocol-compatible with Apple AirDrop so that devices running iOS and macOS can receive from it. Sending web links is supported since v0.13, while OpenDrop receivers still only accept regular files.
What is OpenDrop in the seemoo-lab project?
An open source Apple AirDrop implementation written in Python, produced by reverse engineering work in the Open Wireless Link project and licensed under the GNU General Public License v3.0. It is described as experimental software that might be incompatible with future AirDrop versions and is not endorsed by Apple.
Is opendrop an alternative to AirDrop?
It speaks the same protocol rather than offering a separate one, and it only works where Apple Wireless Direct Link is available: macOS, or Linux running an open re-implementation such as OWL. Receiving uses the receive command, which accepts all incoming files automatically and places them in the current directory.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/seemoo-lab-opendrop)Star history chart for your README
[](https://hysenlabs.com/projects/seemoo-lab-opendrop)Was this useful?