New answers tagged file-encryption
I'm not exactly sure why you are doing what you're doing so my answer may be off-base but I have a couple of ideas. First, being that you're using ASCII to store the data, use more than the 10 digits. Let's also say that we'll use A to mean 0, B to mean 1, through J to mean 9. When you convert to integers, always replace the first digit with the A-J ...
You can use your HardwareID as basis for the encryption key. If the ID provides enough entropy it'll work. However, if anyone can somehow obtain the ID (which might be quite easy to do) one can decrypt the file. For CFB-Mode the IV must indeed be unpredictable (but need not be secret), so random is just fine, but DO NOT REUSE AN IV. Encryption large ...
I did the procedure myself, and I can confirm that base64 decoding will do the trick; the full decrypted file will have == at the end somewhere. After decoding, the "file" command will reveal the plain text type. The '.uyu' file is quite easy to "decrypt" as well, I noted.
As this question is still on the list of "questions without answers", I'll quickly answer it (Basically repeating all of the above comments). Increase iteration count to something larger (1 Million?) You don't want to attach your HMAC of the plain-text after the contents. Rather authenticate either the ciphertext or (even better) use CCM/EAX/GCM mode. ...
Top 50 recent answers are included