Windows or macOS
You can download OnionShare for Windows and macOS from the OnionShare website.
There are various ways to install OnionShare for Linux, but the recommended way is to use either the Flatpak or the Snap package. Flatpak and Snapcraft ensure that you’ll always use the newest version and run OnionShare inside of a sandbox.
Snapcraft support is built-in to Ubuntu and Fedora comes with Flatpak support, but which you use is up to you. Both work in all Linux distributions.
Install OnionShare using Flatpak: https://flathub.org/apps/details/org.onionshare.OnionShare
Install OnionShare using Snapcraft: https://snapcraft.io/onionshare
You can also download and install PGP-signed
.snap packages from https://onionshare.org/dist/ if you prefer.
You can install just the command-line version of OnionShare on any operating system using the Python package manager
pip. Command-line Interface has more info.
Verifying PGP signatures
You can verify that the package you download is legitimate and hasn’t been tampered with by verifying its PGP signature. For Windows and macOS, this step is optional and provides defense in depth: the OnionShare binaries include operating system-specific signatures, and you can just rely on those alone if you’d like.
Packages are signed by Micah Lee, the core developer, using his PGP public key with fingerprint
You can download Micah’s key from the keys.openpgp.org keyserver.
You can find the signatures (as
.asc files), as well as Windows, macOS, Flatpak, Snap, and source packages, at https://onionshare.org/dist/ in the folders named for each version of OnionShare.
You can also find them on the GitHub Releases page.
Once you have imported Micah’s public key into your GnuPG keychain, downloaded the binary and and
.asc signature, you can verify the binary for macOS in a terminal like this:
gpg --verify OnionShare-2.2.pkg.asc OnionShare-2.2.pkg
Or for Windows, in a command-prompt like this:
gpg.exe --verify onionshare-2.2-setup.exe.asc onionshare-2.2-setup.exe
The expected output looks like this:
gpg: Signature made Tue 19 Feb 2019 09:25:28 AM AEDT using RSA key ID CD994F73 gpg: Good signature from "Micah Lee <firstname.lastname@example.org>" gpg: aka "Micah Lee <email@example.com>" gpg: aka "Micah Lee <firstname.lastname@example.org>" gpg: aka "Micah Lee <email@example.com>" gpg: aka "Micah Lee <firstname.lastname@example.org>" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 927F 419D 7EC8 2C2F 149C 1BD1 403C 2657 CD99 4F73
If you don’t see
Good signature from, there might be a problem with the integrity of the file (malicious or otherwise), and you should not install the package. (The
WARNING: shown above, is not a problem with the package, it only means you haven’t defined a level of “trust” of Micah’s (the core developer) PGP key.)