Hello,
I don't understand why i'm getting this error on Windows 10...

Everything is fine when i encrypt file but when I want to decrypt it, I get this error...

Thank's.

Implement -v/--verbose option.

WarShield needs to have less informations by default than now and a verbose mode to display every information.

Expected behavior without verbose:

Scanning files... Done!
Encrypting files... Done!
Elapsed time: 16.27s
Total encrypted files: 1653
Failed: 3 (read-only files)

Expected behavior with verbose:

Added file /etc/nginx/conf.d
Added file /etc/nginx/fastcgi.conf
Added file /etc/nginx/sites-available/default
Added file /etc/nginx/sites-enabled/default
Done encrypting file /etc/nginx/conf.d
Done encrypting /etc/nginx/fastcgi.conf
Done encrypting /etc/nginx/sites-available/default
Done encrypting /etc/nginx/sites-enabled/default
Finished encrypting files!
Elapsed time: 0.76s
Total encrypted files: 4
Failed: 0 (read-only files)

Hi, I am here from your dev.to comment.

I have experience in building a couple of CLIs. I personally prefer CLIs that have an interactive UI. Below is the demo of a CLI that I built for merging PDF files.

In case you are interested in having such an interactive UI for warshield, I'll be glad to help.
If such a UI is not required, let me know if there is anything else that I can do to contribute.
Thank you.

Implement -g/--glob
Implement glob file searching

Command example
warshield encrypt -g "^[a].*$" will encrypt every files that start by the letter a.

Hi,
I was trying to run the CLI. However, I am not able to encrypt any file and always get the following error no matter which file. (I tried to run on both Windows 10 and Ubuntu 18)

As per my knowledge, these files are not read-only and the user does have access to them.
What may be the possible reasons for this error?
Any help in this regard is appreciated. Thank you.

I feel like decrypting the files in place or alongside the encrypted files is a default that is likely to cause disasters.
For instance, if used on an untrustworthy network share, you will end up writing the defenceless files to the network share.
With a usb stick, you might leave the unencrypted files on it (possibly having deleted most but not all).

I would have suggested a temporary directory, but even that doesn't get cleaned up even in case of a reboot in many cases, and users, not being able to locate it, might think it is gone.

This could be a useful feature: an option --single-file (-s) to put every encrypted files in a single file. It could be a zip btw (seems easier with a zip).

The final single file must be ciphered by the way.