Hash code generation for sensitive or encrypted files

[AmeeQAQ]

Issue

As of right now, there is no way of knowing if an attacker has tampered with the encrypted files or the sensitive files generated by the script (AKA encryption keys).

Goals

Generate a hash code each time a file is encrypted, the user changes their password or generates their own keys for the first time.

Possible further enhancements

Investigate about integrating this feature with my previously coded script SHA2Checker

[AmeeQAQ]

Update # 1

So, for now the easiest way to integrate sha2checker.py into this script would be to run it with subprocess.call() and assign it to a variable, so that we can save the exit code.

Concerns

So far the only concern I have is how I implemented the arguments in sha2checker.py. Since it was designed to be a little C-L script, I am not sure how the parser and subprocess.call() will interact with each other. I assume it will only be necessary to just write the arguments like I'd write them in the terminal.

It could also be possible to write a sha2checker lite version especifically for this project. Since it is already very small, this should only take a few mins after everything else is sorted out.

[AmeeQAQ]

Update # 2

It turns out I did not take into account that passing variables as fixed arguments might not be possible 💀.
Did end up doing a sha2checker lite in 1dc1af1 called "sha256chlite". Might not be the most useful thing, and could simply just create a new function in the key management module, but since it uses hashlib, which is easier to use than the message digest functions in crpytography AND it has the file_digest() function which I already know it works for entire files, I just thought it would be better to put it as a separate module.