The NSIS installer appears to have only ever existed as a 32-bit software. As such, unconditionally check the 32-bit registry tree for an uninstall string; the architecture of the current package being installed is not relevant to what was previously installed. ticket: 7362 (new) queue: kfw target_version: 1.10.4 tags: pullup
This installer option determines whether the -autoinit argument is passed to the MIT Kerberos executable. On startup, if this argument is passed, and if there are no tickets in the default cache, and if no useful tickets can be imported from the LSA cache, MIT Kerberos will open the get ticket dialog and prompt for a password; this option does not appear to have any other effect. ticket: 7357 (new) queue: kfw target_version: 1.10.4 tags: pullup
Since the Start Menu and Desktop are different folders, we should use different components for the shortcuts in those folders, given that components operate at directory granularity. Take the opportunity to use the newer style for installing shortcuts and registry keys, and make the names more descriptive. Increment the buildlevel to ensure new files are installed. ticket: 7348 (new) subject: Use more meaningfully named registry keys for shortcuts queue: kfw target_version: 1.10.4 tags: pullup
Signed-off-by: Kevin Wasserman <kevin.wasserman@painless-security.com> ticket: 7341 (new) queue: kfw target_version: 1.10.4 tags: pullup
Signed-off-by: Kevin Wasserman <kevin.wasserman@painless-security.com> ticket: 7338 (new) queue: kfw target_version: 1.10.4 tags: pullup
The InstallValidate action of the windows installer will bring up a dialog informing us that some currently running processes must be terminated before installation may proceed, and offers to do so, but does not actually kill the processes. We have our own code to kill running processes which did not execute, for two reasons: it was sequenced after InstallValidate, and we did not have a current list of processes to look for. Add the right processes to look for and kill, and use our own process-killing code since it actually works. ticket: 7343 (new) queue: kfw target_version: 1.10.4 tags: pullup
Our 64-bit installer provides 32-bit libraries as well as 64-bit libraries, but not all 32-bit applications (e.g., PuTTY, Pidgin) are able to locate them in C:\Program Files\MIT\Kerberos . Including an InstallDir key under the Wow6432Node tree lets them work out-of-the-box; while here set all the registry keys in this component in the compatibility tree, for consistency. ticket: 7337 (new) queue: kfw target_version: 1.10.4 tags: pullup
We use separate UpgradeCodes for 32- and 64-bit installers, so we must check for both of them when seeing if we are upgrading an old/existing installation. ticket: 7335 (new) queue: kfw target_version: 1.10.4 tags: pullup
Instead of using 3.9.9 as a conditional for the maximum version to upgrade from, just use the current version. This seems to pick up beta tags properly (so we can upgrade from, e.g., beta 6 to beta 7 using the installer's upgrade tools), and is future-proof. Note that a 64-bit installer will not pick up an existing 32-bit install (or vice versa), but there does not seem to be infrastructure to deal with this situation easily. Also, "downgrading" by running an older installer with a newer version already installed will cause both versions to be simultaneously installed; only do this if you know what you're doing. ticket: 7334 (new) queue: kfw target_version: 1.10.4 tags: pullup
Replace dogheads with the new 'K'. Signed-off-by: Kevin Wasserman <kevin.wasserman@painless-security.com> ticket: 7330 (new) queue: kfw target_version: 1.10.4 tags: pullup