Building the PKINIT plugin on Windows
kenh at cmf.nrl.navy.mil
Fri Oct 9 15:40:33 EDT 2020
>On 10/9/20 11:39 AM, Ken Hornstein wrote:
>> I guess I'm wondering exactly what kind of infrastructure you want
>> in the Windows build process; do you want to have it build OpenSSL
>> as well, or simply point to already-built OpenSSL libraries?
>Either is okay, but:
>1. We need to be able to document (in src/windows/README) any necessary
>setup for the development environment,
Fair enough; that seems pretty straightforward.
>2. When we build the MSI installer, we presumably need to include
>OpenSSL DLLs, but don't want to conflict with other packages which might
>also depend on OpenSSL, and
I'm a LITTLE unclear on what happens on Windows if you call
LoadLibrary() on a plugin which has a reference to an OpenSSL library
and your application links with another OpenSSL library. We ran into a
problem related to that on Linux. But from a practical matter if the
MSI installer installs the Kerberos libraries in a private directory,
the corresponding OpenSSL libraries would also be installed in the same
>3. I don't want to check OpenSSL sources or binaries into the krb5
I think we're all in agreement here.
BTW, would the license on the Henry Spencer regex library be acceptable?
More information about the krbdev