> <snip> > > > > Therefore, there are numerous occasions in a portable mode situation > > where I need to define "--homedir" in order to have access to the > > keyring, which I have placed on the device. The keyring will always > be > > in the same relative place in relation to the Thunderbird program. > Gpg > > is also installed locally, that is, on the device itself, which is > > basically self contained with the programs needed to run in the > machine's Windows OS. > > Similarly, I can start up the portable TB program with a portable > > Windows command shell so that it looks for the profile in the same > > relative place on the device (using a command "thunderbird.exe -p > > .\data\profile") and so that I can define some other environment > > variables to have constant paths defined relative to the installation > > of the command shell program. However, so that I end up with the gpg > > homedir in the folder where I have the keys in a file on this device > > and accessible to Enigmail, I am right now of the opinion that I > would > > need to define it with the option "--homedir" in the Advanced > > parameters section of Enigmail's configuration settings. I say it > like > > this because this option is the final one and the one that would take > > precedence over any others in terms of the way that gpg determines > > which homedir is to be used for the keyrings. It is, in other words, > > more secure than leaving it to chance that the OS has a predefined > registry setting or environment variable for GNUPGHOME. Is that not so? > > Set GNUPGHOME yourself prior to starting Thunderbird, this overrides > any system definition.
Awesome! I was not sure whether a prior setting within the OS would take precedence or possibly get picked up inadvertently. This possibility is one reason why I want to use my chosen command shell, the portable one, to prevent the operating system's shell from injecting its variables into my work. It is precautionary. >See below for using values relative to the > command shell script. > > >> One last thought, what is it you wish to accomplish and why? When > one > >> requires configuration that no one else has mentioned in a decade, > it > >> leads me to think the use case is what needs to be examined. > > > > See above. > > Stating the what and why often leads to a much more concise answer. Yes, I do need to work on my brevity. I have been trained to the opposite extreme, and forcing myself not to indulge is taking a goodly amount of effort, albeit a worthwhile one. > In your bat file for starting Portable Thunderbird, include a line near > the top similar to > > SET GNUPGHOME=%~d0\GnuPG > > This will expand to <drive letter>:\GnuPG > > If your script for starting Portable Thunderbird is > <drive>:\PortableApps\Thunderbird.bat, then %~dp0 will expand to > <drive>:\PortableApps, i.e., the _D_rive and the _P_ath of the called > command script. It occurs to me that I might use %~p0 in order to cover the case when there is no drive letter but only a UNC pathname. I will test it. > --homedir can be useful when one is doing things with the gpg command > line, but it's not a very good solution in scripts, IMO > > -John > > http://stackoverflow.com/questions/5034076/what-does-dp0-mean-and-how- > does-it-work > Good link. Talk to you later. John A. Wallace _______________________________________________ enigmail-users mailing list [email protected] https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
