download
get veil
One free download, no account, no email gate. Linux is real today. Windows is planned — shown honestly, not offered.
Nothing to install first. The binary is statically linked, so there is no glibc version to match and no libraries to fetch — it runs the same on Debian, Alpine and everything in between. Read-only checks; nothing on your machine changes unless you run a specific fix.
download for linux want one single file instead? get the AppImage → what it does on linux →There is no windows build. This is not a disabled button dressed up as a feature — it's an honest "not yet." See the platform page for exactly what will and won't work once it ships.
what it will do on windows →if it doesn't open
your desktop asking "what should I open this with?"
That is the executable bit, not a broken download. A web server has no way to mark a file runnable, so every browser saves it without permission to run. Extracting the .tar.gz normally restores it for you. If your file manager stripped it anyway, open a terminal in that folder and run this:
chmod +x veil && ./veil
The .tar.gz needs nothing else. The AppImage is the one exception — a few distros no longer ship the FUSE library it mounts itself with. If the AppImage exits complaining about FUSE, you can either use the .tar.gz above and skip the problem entirely, or run it without mounting:
APPIMAGE_EXTRACT_AND_RUN=1 ./veil-0.2.1-x86_64.AppImage
or install FUSE for your distro
sudo apt install libfuse2
Not listed? Your distro packages it under some spelling of fuse2 or libfuse2 — search your package manager for "fuse". If you would rather not install anything at all, the .tar.gz is the answer.
verify the download
check the checksum before you run anything
A checksum confirms the file you downloaded is byte-for-byte what was published — not that the publisher is trustworthy, just that nothing altered it in transit or on a mirror. Compare it yourself; don't take our word that it matches.
veil-0.2.1-x86_64-static.tar.gz
veil-0.2.1-x86_64.AppImage
Both are published as SHA256SUMS on the release itself, so you can check them against the source rather than against this page.
-
compute the hash locally
Linux:
sha256sum veil-0.2.1-x86_64-static.tar.gz. Windows (once a build exists):certutil -hashfile veil.exe SHA256. -
compare, character by character
The output must match the checksum above exactly. If it doesn't, don't run the file — re-download from the original release link, not a mirror.
what happens when you open it
the plain, unglamorous reality per OS
AppImage, no signature dialog
- most distros don't gate unsigned binaries the way Windows does — you chmod +x it and it runs.
- some desktop environments show a "trust this executable?" prompt the first time — that's your file manager, not veil, asking.
- no code-signing certificate exists for this build. Verify the checksum instead of trusting a signature that isn't there.
expect SmartScreen, once it ships
- a solo developer's .exe has no reputation with Microsoft's SmartScreen — expect an "unrecognized app" warning even on a legitimate, unmodified build.
- a paid EV code-signing certificate is the only way to skip that warning, and it costs real money yearly for no functional benefit — that trade isn't made yet.
- clicking through the warning after verifying the checksum yourself is a reasonable choice; clicking through it blind is not.