gnupg feature request

[Mark H. Wood]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 8 Dec 2003, Jim C. wrote:
[snip]
> Here is the output of a registry export for an XP Pro box for anyone who
> wants it.
>
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\GNU]
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\GNU\GNUPG]
> "gpgProgram"="C:\\Program Files\\GnuPG\\gpg.exe"

This much is quite proper (and the path is *much* more proper than the
default C:\GnuPG).

> "HomeDir"=hex(2):25,00,41,00,50,00,50,00,44,00,41,00,54,00,41,00,25,00,5c,00,\
> ~  47,00,6e,00,75,00,50,00,47,00,00,00

I have wondered whether REG_EXPAND_SZs are automagically expanded by the
Registry access functions or just exist as a clue that the app. should
expand the strings, but was too lazy to do the experiment.  Thanks for
clearing that up!  However, the path to the user's keyrings should be a
per-user setting, so it belongs in HKCU.  The above works, but it is
common to every user so they all have to keep their keyrings in the same
place relative to their usernames.  In particular, I might prefer to keep
my keyrings on a central server and use them from there, instead of
leaving various stale copies all over the campus in roaming profile
images.  (IMNSHO about 98% of the stuff in a user's profile belongs
elsewhere.)

- -- 
Mark H. Wood, Lead System Programmer   mwood at IUPUI.Edu
MS Windows *is* user-friendly, but only for certain values of "user".
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: pgpenvelope 2.10.2 - http://pgpenvelope.sourceforge.net/

iD8DBQE/4cZ8s/NR4JuTKG8RAr4iAJsF1RmpxNjekzVs6FNyzqs2SQfgawCfcfqR
5HbSBcW3XE/i9IRyXY0g7kQ=
=WSDi
-----END PGP SIGNATURE-----