New Cloaker 4.0 downloads on the Releases page!

Mobile version available at https://cloaker.mobi! Static HTML/CSS/JS/WASM and interoperable with this version of Cloaker. Code here.

Have you ever wanted to protect a file with a password and found it unnecessarily difficult to do so? Cloaker aims to provide the most straightforward file encryption possible. Just drop a file onto the window, set a password, and choose where to save it. To decrypt, drop the encrypted file on the window, enter the password, and choose the output location. No installation required: on Windows it's a single .exe, on Mac an .app bundle, and on Linux a single executable .run file.

Data Loss Disclaimer: if you lose or forget your password, your data cannot be recovered! Use a password manager or another secure form of backup. Cloaker uses the pwhash and secretstream APIs of libsodium via sodiumoxide.

cd cloaker/adapter; cargo build --release.

Then open gui/cloaker/cloaker.pro in Qt Creator (Qt 5.15.2), make sure kit is 64bit, and build.

If you want to make a distributable on...

Mac: use the macdeployqt script in your Qt installation's bin/ directory with the built .app bundle as argument.

On Linux and Windows: make sure Sources are installed for Qt 5.15.2 through the Qt Maintenance Tool.

Linux Mint 20: compiling Qt statically is a dark and arcane practice that I've wasted way too much time trying to understand. These instructions build a static version of Qt on Mint 20, and programs built with that Qt version run on a fresh installation of Ubuntu 20. However, you may still find libraries missing if you try to use the Cloaker 4.0 binary from the releases page on other distros. If you have trouble, open an issue, and I'll see if I can help. (Or, if you're using Linux, you might just want to use the CLI version which is much easier to compile.)

Install dependencies (partially-helpful reference here):

sudo apt install build-essential # C/C++ compiler
sudo apt install ^libxcb.*-dev # installs all libxcb dev packages
sudo apt install libx11-xcb-dev
sudo apt install libxkbcommon-dev libxkbcommon-x11-dev libglib2.0-dev libgtk-3-dev # keyboard, glib, and gtk packages we'll need for the flags we're going to use with the `configure` script

Then compile Qt statically with something like

$ mkdir ~/qt-static; cd ~/qt-static
$ ~/Qt/5.15.2/Src/configure -static -release -opensource -confirm-license -skip multimedia -skip webengine -skip wayland -no-compile-examples -nomake examples -no-openssl -no-opengl -ico -xcb -gif -gtk -qt-pcre -bundled-xcb-xinput
$ make -j8

More documentation on the configure command can be found here, and all the options can be seen by running ~/Qt/5.15.2/Src/configure -h. Other helpful resources are the pages on Linux deployment and X11 requirements.

Windows only: install Visual Studio 2019 Community (including the Desktop development with C++ feature), launch the x64 Native Tools Command Prompt (found in Start Menu > Visual Studio 2019) and compile Qt statically with something like:

> cd C:\; mkdir qt-static; cd qt-static
> C:\Qt\5.15.2\Src\configure.bat -release -static -no-pch -optimize-size -opengl desktop -platform win32-msvc -skip webengine -nomake tools -nomake tests -nomake examples
> nmake.exe

Run rustup default stable-x86_64-pc-windows-msvc to make sure you're using MSVC, and rerun cargo build --release from adapter/ if you weren't.

Finally, on Linux and Windows: go to Qt Creator > Project > Manage Kits > Qt Versions, add a new version of Qt, and point to ~/qt-static/qtbase/bin/qmake or C:\qt-static\qtbase\bin\qmake.exe. Add a new Kit in the Kits tab, and set its Qt version to be the static one you just added. On the Projects page, click the plus button by the new Kit under Build & Run. Now you can build with the static kit's Release profile in the bottom-left above the play and build buttons.

cd cli; cargo build --release. Executable will be at cloaker/cli/target/release/cloaker_cli(.exe).

• Change minimum password length to 14 or 16?

• Please tell me about them.
• Backward compatibility notes:
  • to decrypt a file made with version 1.0 or 1.1 of Cloaker (with Encrypt and Decrypt buttons), the filename must end with the ".cloaker" extension. Files encrypted with later versions are not subject to this restriction.
  • Cloaker version 4 can decrypt files that were encrypted with previous versions, but previous versions cannot decrypt files encrypted with version 4+.

If you've used Cloaker, please send me feedback and thank you for your interest!

You might also like: https://github.com/spieglt/flyingcarpet