encrypting deleted file, can't decrypt even with correct key.

[BMaxV]

Hi, I tried to use this,

I entered "asdfasdf" as the Key (B) selected a file, encrypted.

It deleted the old file, which I think is bad behavior.

And when I entered "asdfasdf" in Key(H) to decrypt it didn't work. I inserted the nonce too, no idea what that is or why but that fit. But the Key(H) seems to be wrong.

So now I can't decrypt the file. It was a throw away file, so that's not an issue.

How do I get the "Key(H)"?

[paulz1]

I'd like to support this issue, as I have pretty the same.

• deleting the original file is managed in the Menu-> Main Settings (or Options.txt file)
  But could/should it be setup to False by default ?

• The same for key in Database.
  There is an option in Menu -> DB Settings : Delete key/nonce after decryption

Should it be set to False by default.
I didn't see this option at first. So

1. I encrypt test-file (got test-file.encex)
2. remove test-file (rm test-file)
3. decrypt test-file.encex : as it was stored in DB it load key/nonce automatically
4. check the decrypted test-file is the same as the original
5. the check was good, so I remove this new decrypted-file

But at point 3, key/nonce pair was removed from DB, so if I load test-file.encex again it could not be decrypted (no key/nonce in DB).

• And so the biggest question, how to decrypt the file if I know the key, but it's not in DB ?

To decrypt the file it wants key in hex format. I could convert my key into hex format.
But...

1. If I compare my converted to hex key, with the key stored in DB they are not the same. They are similar, but key stored in DB has some additional symbols at the end.
   For example the end of my key in hex format is : ...313131
   But the same key stored in DB shows : ...31313110101010101010101010101010101010
   Is it normal ?

2. What is "nonce" and how to get it ?