Kerberos for Windows Release Engineering - Revision history

Ghudson at 17:41, 5 April 2026

2026-04-05T17:41:06Z

Ghudson at 17:13, 7 April 2019

2019-04-07T17:13:37Z

TomYu at 22:32, 27 June 2016

2016-06-27T22:32:06Z

TomYu at 18:44, 11 April 2016

2016-04-11T18:44:54Z

TomYu at 22:21, 8 April 2016

2016-04-08T22:21:08Z

BenKaduk: List the steps involved in building the official release binaries

2015-06-25T22:04:56Z

List the steps involved in building the official release binaries

BenKaduk at 19:40, 19 September 2012

2012-09-19T19:40:48Z

BenKaduk: we resolved some issues

2012-09-17T19:21:03Z

we resolved some issues

BenKaduk at 19:19, 17 September 2012

2012-09-17T19:19:49Z

BenKaduk at 17:04, 22 August 2012

2012-08-22T17:04:43Z

@@ Line 42: / Line 42: @@
 ** In src/windows/winlevel.h, increment KRB5_BUILDLEVEL.  If this is the first KfW commit on the branch, leave it at 0.
 ** Tag this commit with the release tag name with the suffix "-mit".
 ** Create a source zip achive with "git archive --prefix=<tagname> --format=zip -o /path/to/<tagname>-src.zip <tagname>".  Sign it with gpg -ab filename.zip to produce the detached .asc signature.
 ** Build this release with "set NODEBUG=1" and "set MIT_INTERNAL=1".

@@ Line 1: / Line 1: @@
 [[Category: Kerberos for Windows]]
-Release Engineering notes for the Kerberos for Windows 4.0.0 release
+Release Engineering notes for the Kerberos for Windows 4.2.0 release
 Software to test against new builds:
@@ Line 24: / Line 24: @@
 Current known issues:
 * The version number implanted in various dlls no longer reflects the underlying krb5 version (instead using the KfW version); this may not actually be a bug.
 * (Version) upgrades that go from 64-bit to 32-bit leave 64-bit binaries around but otherwise succeed.
 Use the arCHMage package to extract HTML from the CHM file for the web. The tool outputs some bogus absolute URLs for links and inline images, so use

← Older revision		Revision as of 22:32, 27 June 2016
Line 123:		Line 123:

	On the VM host, extract the build output for signing.		On the VM host, extract the build output for signing.
		+
		+	Use the arCHMage package to extract HTML from the CHM file for the web. The tool outputs some bogus absolute URLs for links and inline images, so use
		+
		+	perl -pi -e 's,((?:href\|src)=")/,\1../,g' /
		+
		+	to postprocess.

← Older revision		Revision as of 18:44, 11 April 2016
Line 1:		Line 1:
		+	[[Category: Kerberos for Windows]]
	Release Engineering notes for the Kerberos for Windows 4.0.0 release		Release Engineering notes for the Kerberos for Windows 4.0.0 release

← Older revision		Revision as of 22:21, 8 April 2016
Line 34:		Line 34:
	* Our DllMain attach/detach handler spews to the terminal when running command-line utilities. Possibly other debug print statements, too.		* Our DllMain attach/detach handler spews to the terminal when running command-line utilities. Possibly other debug print statements, too.

		+	Versioning stuff:
		+
		+	* src/patchlevel.h
		+	* src/windows/installer/wix/site-local.wxi
		+	* src/windows/version.rc (copyright year)
		+	* src/windows/winlevel.h
		+	* src/windows/kerberos.ver

	Procedure for building release binaries (MIT and non-MIT, i386 and amd64):		Procedure for building release binaries (MIT and non-MIT, i386 and amd64):

← Older revision		Revision as of 22:04, 25 June 2015
Line 33:		Line 33:
	* Thunderbird cannot do GSSAPI auth unless you disable SSPI		* Thunderbird cannot do GSSAPI auth unless you disable SSPI
	* Our DllMain attach/detach handler spews to the terminal when running command-line utilities. Possibly other debug print statements, too.		* Our DllMain attach/detach handler spews to the terminal when running command-line utilities. Possibly other debug print statements, too.
		+
		+
		+	Procedure for building release binaries (MIT and non-MIT, i386 and amd64):
		+
		+	On the VM host:
		+
		+	rm -rf /path/to/share/kfw-4.1-beta2 && git archive --prefix=kfw-4.1-beta2/ [committish] \| (cd /path/to/share/; tar x)
		+	rm -rf /path/to/share/kfw-4.1-beta2-mit && git archive --prefix=kfw-4.1-beta2-mit/ [committish] \| (cd /path/to/share/; tar x)
		+	git archive --prefix=kfw-4.1-beta2/ --format=zip -o ../kfw-4.1-beta2-src.zip refs/tags/kfw-4.1-beta2
		+
		+
		+	mkdir C:\destdir
		+	mkdir C:\debug-symbols
		+	mkdir C:\debug-symbols\kfw-NNN-i386-mit
		+	mkdir C:\debug-symbols\kfw-NNN-amd64-mit
		+	mkdir C:\debug-symbols\kfw-NNN-i386
		+	mkdir C:\debug-symbols\kfw-NNN-amd64
		+	setenv /x86 /release
		+	set CPU=i386
		+	set KRB_INSTALL_DIR=C:\destdir
		+	set NODEBUG=1
		+	set DEBUG_SYMBOL=1
		+	set MIT_INTERNAL=1
		+	# do the MIT i386 build
		+	cd C:\kfw-NNN-mit\src
		+	nmake -f Makefile.in prep-windows
		+	nmake
		+	nmake install
		+	set DEBUG_SYMBOL= # unset it
		+	mv C:\destdir\bin\*.pdb C:\debug-symbols\kfw-NNN-i386-mit
		+	cd windows\installer\wix
		+	nmake
		+	rename kfw.msi kfw-NNN-i386-mit.msi
		+	# time for the MIT amd64 build
		+	cd ..\..\..
		+	setenv /x64 /release
		+	set CPU=AMD64
		+	set DEBUG_SYMBOL=1
		+	nmake clean
		+	nmake
		+	nmake install
		+	set DEBUG_SYMBOL= # unset it
		+	mv C:\destdir\bin\*.pdb C:\debug-symbols\kfw-NNN-amd64-mit
		+	cd windows\installer\wix
		+	nmake clean
		+	nmake
		+	rename kfw.msi kfw-NNN-amd64-mit.msi
		+	rm -r C:\destdir\bin
		+	rm -r C:\destdir\lib
		+	rm -r C:\destdir\include
		+	# fresh env for the non-MIT i386 build
		+	setenv /x86 /release
		+	set CPU=i386
		+	set DEBUG_SYMBOL=1
		+	set MIT_INTERNAL= # unset it
		+	cd C:\kfw-NNN\src
		+	nmake -f Makefile.in prep-windows
		+	nmake
		+	nmake install
		+	set DEBUG_SYMBOL= # unset it
		+	mv C:\destdir\bin\*.pdb C:\debug-symbols\kfw-NNN-i386
		+	cd windows\installer\wix
		+	nmake
		+	rename kfw.msi kfw-NNN-i386.msi
		+	cd ..\..\..
		+	# the non-MIT amd64 build
		+	setenv /x64 /release
		+	set CPU=AMD64
		+	set DEBUG_SYMBOL=1
		+	nmake clean
		+	nmake
		+	nmake install
		+	set DEBUG_SYMBOL= # unset it
		+	mv C:\destdir\bin\*.pdb C:\debug-symbols\kfw-NNN-amd64
		+	cd windows\installer\wix
		+	nmake clean
		+	nmake
		+	rename kfw.msi kfw-NNN-amd64.msi
		+	[copy C:\kfw-NNN{,-mit}\src\windows\installer\wix\*.msi to the shared drive]
		+	[recursively copy C:\debug-symbols\kfw-NNN* to the shared drive]
		+
		+	On the VM host, extract the build output for signing.

@@ Line 22: / Line 22: @@
 Current known issues:
-* The version number implanted in various dlls may no longer reflect the underlying krb5 version (instead using the KfW version)
+* The version number implanted in various dlls no longer reflects the underlying krb5 version (instead using the KfW version); this may not actually be a bug.
 * windows/README is outdated
 Issues that we believe to be resolved:

@@ Line 7: / Line 7: @@
 * SPNEGO (in multiple browsers?)
 * Adobe Keyserver a.k.a the Sassafras key client
 * LDAP in some form?
-* XMPP in some form (pidgin?)?
+* XMPP via, e.g., Pidgin
 Upgrades scenarios to test:

@@ Line 19: / Line 19: @@
 * 64-bit to 32-bit, from 4.0
 When starting from 3.2, it probably suffices to test the Secure Endpoints versions once only, and assume that there will not be future changes to 4.0 which cause the upgrade process to fail for the SE version but not the MIT-distributed version.
 Current known issues: