Chris
Chris
Using a new `naked` function `piperun` to pipe the passphrase through `stdin`. Requires to update `naked` framework. (Pull request submitted: https://github.com/chrissimpkins/naked/pull/8)
It could be useful at times to allow the user to provide the passcode at the time of calling crypto. It is partially related to issue #8, but not really...
It seems parallel execution of multiple instances of gpg could vastly increase the performance over the current iterative approach. Since the same passcode is used for all files anyway, it...
Using `multiprocessing` it is now possible to encrypt files in parallel, with however many parallel threads the user chooses. A new option `--parallel [#N]` with a **non-optional** argument for the...
How could we validate that the encryption was really successful after completion? I assume such an option (e.g. `--validate` or `--verify`) would be a good addition to `crypto`. The only...
Generally, when you encrypt files, it might make sense to delete the _original_ and only keep the encrypted version (this is probably not the default behaviour the users expect, but...
An important aspect of encryption before syncing files in a cloud-storage-space is file-name-encryption. It would be great to see (an option) to encrypt/decrypt file names. This might not be terribly...
As described in #10 - this would add an option to input the passphrase through the command-line. The new option is called `--passphrase` and requires an option afterwards. I implemented...
I have done some basic testing and couldn't find any issues so far. I simply called this option "--name" for encryption as well as decryption. Some things to note: 1...
A menu-bar icon is nice and I am very happily using it already. It would generally be great, if the menu-bar icon would gain more functionality - generally when thinking...