File Encryption (and Decryption) Made Easy

Marco Massenzio
2 min readAug 30, 2017

--

Keys, keys… where are my keys?

A new release of the Crytto library (0.4.0) has just been published, which greatly simplifies encrypting (and decrypting) files

The new release adds the decrypt script which, when combined with the existing automatic retrieval of the encryption key from the keystore, makes it a breeze to decrypt files.

For example, if you had encrypted your file with:

$ encrypt --keep README.md

the file would have been saved either in the same directory, or where you had configured the out: directory:

[INFO ] File 'README.md' encrypted to '/var/tmp/README.md.enc' 
[INFO ] Encryption successful; saving data to store file '/private/archive-pass/keys.csv'.

To decrypt it back, then it will just be a matter of:

$ decrypt --out ${HOME}/README.md /var/tmp/README.md.enc [INFO ] File '/var/tmp/README.md.enc' decrypted to '/private/README.md'

The configuration YAML file is now by default kept in ${HOME}/.crytto/conf.yml and its contents haven’t changed.

In addition, to keep the keystore in a reasonably “clean” state, we have added the prune_store script, which removes from the CSV file all the entries relative to files that no longer exist (use with care: if files have been moved the prune_cmd script won’t be able to detect that and you may lose valuable information – however, a copy of the keystore is kept in a .bak copy).

More information available in the GitHub repository.

Originally published at codetrips.com on August 30, 2017.

Sign up to discover human stories that deepen your understanding of the world.

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

--

--

No responses yet

Write a response