MIT KFW 4 - Enforce copy of krb5.ini to system32 directory

[Dejan Gregor]

Hi Ben,

thank you for the steer, appreciate the explanation on how the order of
locations of configuration file is called.

Will keep it as is.

Dejan

On 20 June 2015 at 20:46, Benjamin Kaduk <kaduk at mit.edu> wrote:

> On Sat, 13 Jun 2015, Dejan Gregor wrote:
>
> > Hello,
> >
> > I have a requirement to copy our custom krb5.ini to the
> C:\Windows\System32
> > directory. I have unpacked the MSI after compiling it with WIX (delivered
> > by MIT) and have confirmed our custom krb5.ini is embedded in the
> > executable.
> >
> > Where and what to change in the WIX configuration (for 32-bit build) to
> > enforce copy of custom krb5.ini to the C:\Windows\System32 directory?
>
> It is actively discouraged for applications other than the OS to put
> anything in the system32 directory; do you have a good reason for needing
> to do so?
>
> Note that several paths are searched for krb5.ini prior to
> C:\Windows\system32 -- in particular, CSIDL_APPDATA, CSIDL_COMMON_APPDATA,
> and the location of the krb5_{32,64}.dll in use.  (There is also a
> registry key which can specify the path of the krb5.ini to use.)  The KfW
> 4.x series installer places its krb5.ini in the common appdata folder, to
> make it available to all users in a way consistent with current best
> practices.
>
> That said, if you are convinced that you need to deviate from the current
> best practices and use the system32 folder, you can change the parent
> <Directory> elements of the <File> element with Id attribute fil_krb5_ini,
> in src/windows/installer/wix/files.wxi, and rebuild the installer.  I
> think you could also use orca.exe to modify the component table and put
> the cmf_krb5_ini component in a different directory, but I haven't tested
> that.
>
> -Ben
>