Sometimes it gets an error "gpg.exe not found".
Restarting Outlook or re-entering the path in the settings (while it was already there) usually fixes the problem.
I first thought I was the only one to have the problem but Dirk had also the same issue the very first time he tried the plugin, with v1.9.0.1, while path to gpg.exe was properly set in the dialog box...
Now the internal error could be sth else and the error message simply misleading, no idea for the moment :(
EDIT:
Sometimes the path contains gpg.exe and sometimes not.
E.g. in OutlookGnuPG.cs GetPrivateKeys() and GetKeys():
string gnuPath = _gnuPg.BinaryPath;
if (!gnuPath.EndsWith("gpg.exe"))
_gnuPg.BinaryPath = Path.Combine(gnuPath, "gpg.exe");
GnuPGKeyCollection privateKeys = _gnuPg.GetSecretKeys();
_gnuPg.BinaryPath = gnuPath;
seems to be a workaround to the fact that in starksoft we have
string gpgPath = string.IsNullOrEmpty(_binaryPath) ? Path.Combine(GetGPGInstallLocation(), GPG_EXECUTABLE) : _binaryPath
so _binaryPath supposed to contain gpg.exe while at other places _binaryPath is initialized with GPG_COMMON_INSTALLATION_PATH or with _settings.GnuPgPath which don't contain the gpg.exe
So my guess is that all gpg paths should be checked through the code to never contain gpg.exe, remove the hack in GetPrivateKeys() and GetKeys() and fix starksoft openpgp.
doegox
commented
14 years ago
Sometimes it gets an error "gpg.exe not found". Restarting Outlook or re-entering the path in the settings (while it was already there) usually fixes the problem.
I first thought I was the only one to have the problem but Dirk had also the same issue the very first time he tried the plugin, with v1.9.0.1, while path to gpg.exe was properly set in the dialog box...
Now the internal error could be sth else and the error message simply misleading, no idea for the moment :(
EDIT: Sometimes the path contains gpg.exe and sometimes not. E.g. in OutlookGnuPG.cs GetPrivateKeys() and GetKeys(): string gnuPath = _gnuPg.BinaryPath; if (!gnuPath.EndsWith("gpg.exe")) _gnuPg.BinaryPath = Path.Combine(gnuPath, "gpg.exe"); GnuPGKeyCollection privateKeys = _gnuPg.GetSecretKeys(); _gnuPg.BinaryPath = gnuPath; seems to be a workaround to the fact that in starksoft we have string gpgPath = string.IsNullOrEmpty(_binaryPath) ? Path.Combine(GetGPGInstallLocation(), GPG_EXECUTABLE) : _binaryPath so _binaryPath supposed to contain gpg.exe while at other places _binaryPath is initialized with GPG_COMMON_INSTALLATION_PATH or with _settings.GnuPgPath which don't contain the gpg.exe
So my guess is that all gpg paths should be checked through the code to never contain gpg.exe, remove the hack in GetPrivateKeys() and GetKeys() and fix starksoft openpgp.