On Thu, 26 May 2005 02:22:06 -0700, t takahashi said: > another example of unnecessary accessing of homedir is when you want > to compress a file. when you do gpg --store, homedir access is unnecessary > but gpg tries to access it (perhaps to find preferences?). however, there is > no way to turn off its errors or have it simply default.
GnuPG requires is home directory for internal purposes and you should not fiddle around with it. We can't use /var/lib/gnupg because these information are per-user and partly confidential. There is a reason why the default home directory is hidden (.gnupg) - this indicates local configuration data and internal data required for proper operation. Using this data is on your own risk. There is a documented interface on how to access it (--export/--import etc.). You are on your own if you work outside of the specification. GnuPG 1.9 for example adds other objects to the home directory. BTW, never ever look at any data printed for human reading - scripts need to parse the --status-fd and --with-colon output. For controlling gpg aside from this, the --command-fd/--status-fd interface is the way to go. Please don't use canned commands but parse the requests seen on --status-fd before sending commands to gpg - if there is something you can't cope with: bail out. Note that in most cases using the default response (which is sending an empty string) leads to proper results. Salam-Shalom, Werner -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
