Global value of --homedir

[GoogleCodeExporter]

What steps will reproduce the problem?
--------------------------------------
1. Place your public and secret keyrings in a non-standard location, like U:\PGP
2. Bring up Cryptophane's GUI, or use any of the right-click extensions.  
Observe no public or private keys.
3. Attempt to modify the shortcut for Cryptophane and the Registry for things 
like HKCR\*\shell\cryptophane\command and realize that it gets overwritten 
every time Cryptophane loads. 

What is the expected output? What do you see instead?
-----------------------------------------------------
If there were a way to change the definition of --homedir globally within the 
GUI, the multiple ways Cryptophane can be executed wouldn't all have to be 
modified via command-line switches.  This is especially true when attempting to 
use either GnuPG or Cryptophane in a portable fashion.

What version of the product are you using? On what operating system?
--------------------------------------------------------------------
Cryptophane 0.7.0 under Windows XP.

Please provide any additional information below.
------------------------------------------------
Please consider adding an additional Option to globally override the default 
location (homedir) of keyrings, the trustdb, and possibly gpg.conf.  Currently, 
there is no practical way to use all of the features and conveniences of 
Cryptophane when the user's keys are in a non-default location.

Alternately, read in the value of HKCU\Software\GNU\GnuPG\HomeDir and use that 
as the default --homedir for the GUI.

Original issue reported on code.google.com by ViperG...@gmail.com on 1 Sep 2011 at 9:53

[GoogleCodeExporter]

Heinous Workaround:
-------------------
Execute the attached .REG file (customize for homedir location).

Then use RegEdit to change the permissions of HKCR\*\shell\cryptophane, 
HKCR\Cryptophane.Encrypted.1, and HKCR\Cryptophane.Signature.1 to (Everyone = 
Read Only) so Cryptophane can't re-reset the registry keys.

Strangely, even adding the --no-config and/or --memstick options cause 
Cryptophane to overwrite these three Registry keys.

Original comment by ViperG...@gmail.com on 2 Sep 2011 at 2:34

Attachments:

• Cryptophane.reg

[GoogleCodeExporter]

Sigh ...

I found a /much/ easier "workaround" by perusing the source code in SVN.  
Apparently there's an undocumented file called cryptophane.ini that, if it 
exists, will override some of the defaults.  See attached.

Original comment by ViperG...@gmail.com on 2 Sep 2011 at 2:43

Attachments:

• Cryptophane.ini