Secure and resilient remote file storage utility https://e.xtendo.org/scs/unbreak
|Latest on Hackage:||0.3.1|
This package is not currently in any snapshots. If you're interested in using it, we recommend adding it to Stackage Nightly. Doing so will make builds more reliable, and allow stackage.org to host generated Haddocks.
unbreak is a minimal helper utility to have files accessible, encrypted, and stored remotely, even with an unstable Internet connection. Questions, bug reports, feature requests, and pull requests are welcome.
Current version: 0.3.1 (changelog)
See unbreak's web page for more details.
Build from git source
Stack is the recommended tool to build the latest git version of unbreak.
$ git clone --depth=1 https://github.com/kinoru/unbreak $ cd unbreak $ stack install
0.3.1 - 2015-12-30
- Changed wrong error messages and improved existing messages.
- Added necessary fields to unbreak.cabal.
- Applied wild.
0.3.0 - 2015-12-15
- The command line arguments interface has changed to multi-mode. Users are now advised to set
uas an alias of
unbreak open <FILENAME>
unbreak add [OPTIONS] <FILENAME>
unbreak add: Pick a local file, encrypt it, and put it in the remote storage
unbreak logout: Explicitly remove the session files from the memory space.
- Added automatic removal of local temporary files in the memory space after
- Added upload error remedy to
unbreak open: the user's effort won't be immediately lost even when the upload fails. Now there is a chance to retry or save it somewhere else.
- Fixed file name encryption: Very silly elemetary cryptographic mistake. Eliminated the chance of adversary guessing the file name when there are multiple files with the same prefix.
0.2.0 - 2015-12-09
- Added encryption of file names: File names may be a sensitive information as well. They are now encrypted with ChaCha20-Poly1305 and base64url-encoded.
- Avoid network overhead by checking file mtype: The file won't be sent if it hasn't been changed.
0.1.0 - 2015-12-05
- Prepended a single byte in the encrypted file format to indicate the "version number." The byte isn't really used for anything useful yet; it's for forward compatibility.