salsi9 / cryptophane

Automatically exported from code.google.com/p/cryptophane
GNU General Public License v2.0
0 stars 0 forks source link

Retrieving Previous Cryptophane Files - After Re-installation #30

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Generate secret key, encrypt a file, reformat HDD
2. Reinstall Windows, recover cryptophane files
3. Attempt to access encrypted file after reinstalling cryptophane and pasting 
old files into appdata\roaming\gnupg "default folder I believe" The files I 
pasted are pubring.bak, pubring.gpg, random_seed, secring.gpg, and trustdb.gpg

What is the expected output? What do you see instead?
Replaced files from old HDD would change cryptophane back to how it was on the 
old HDD and allow me to access my files.

What version of the product are you using? On what operating system?
cryptophane-0.7.0-gnupg-1.4.2.exe on Windows 7

Please provide any additional information below.
I recently install cryptophane, generated a secret key, encrypted a file, then 
reinstalled windows. I thought that all I would need was the password 
associated with the file, clearly I was ignorant. Now whenever I try to open 
the file I get "The secret key <unkown key EEFQ1456RWQ> is required to decrypt 
this data, but was not found.

I thought that recovering the files listed above (pubring, secring, etc) and 
placing them in the default appdata roaming location that cryptophane places 
these files in when it creates a new key from scratch would give me back the 
functionality I had before I reinstalled. Is there no way to ever get this 
information back? Am I not placing the files in the right place? Are there more 
files I need for this to work? Is there any way to skip the key and go straight 
to the password?

Btw, I have tried changing the info in crytophane.ini to change the homedir, 
but it never adds the keys. I have also uninstalled (and also deleted the 
appdata folder) to try and do a clean install with the old hdd files.

Original issue reported on code.google.com by flory....@gmail.com on 18 Jun 2014 at 3:40