Skip Menu |

Download (untitled) / with headers
text/plain 2.9KiB
From Wed Jan 8 09:48:43 1997
Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU []) by rt-11.MIT.EDU (8.7.5/8.7.3) with SMTP id JAA06046 for <bugs@RT-11.MIT.EDU>; Wed, 8 Jan 1997 09:48:42 -0500
Received: from [] by MIT.EDU with SMTP
id AA20853; Wed, 8 Jan 97 09:48:40 EST
Received: from [] by
id 20033687.0; Wed, 08 Jan 97 14:48:27 GMT
Received: by with Microsoft Mail
id <>; Wed, 8 Jan 1997 09:51:49 -0500
Message-Id: <>
Date: Wed, 8 Jan 1997 09:51:47 -0500
From: Sean Moore <>
To: "''" <krb5-bugs@MIT.EDU>
Subject: NT ALPHA1 GSS fixes

Show quoted text
>Number: 336
>Category: krb5-appl
>Synopsis: NT ALPHA1 GSS fixes
>Confidential: yes
>Severity: serious
>Priority: medium
>Responsible: basch
>State: closed
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Wed Jan 08 09:49:01 EST 1997
>Last-Modified: Fri Feb 07 15:26:14 EST 1997
>Release: 1.0alpha1
sorry to be sending directly to this list but krb5-send-pr
does not run on NT.

I am interested in GSS for NT so I was very excited about
the NT alpha. I have both the GSS client and server working
on NT so here are the steps I had to go through.

problem: GSS client would not run
fix: needed the rc file to link with the exe also

problem: GSS client name lookup failed
fix: needed to add wsastartup and wsacleanup to program

problem: gpf on a free of memory in GSS-api library
fix: change all compiles to use the DLL c library
a) I added to CCOPTS and CCOPTS2
/MDd /D"_DEBUG" /D"_MT" /D"_DLL"
for a debug build.
b) removed /nod and /libc from link lines

The reason this fixes the problem is that the
Krb5 dll and GSS dll were both linked with the
static c library meaning they both have there
own heap. This is fine if everything a dll
allocs it also frees. This is not the case so
linking with the dll c library fixes this problem.

problem: gpf after error dialog display (ie expired ticket)
fix: change KRB5_EXPORTVAR from _export to _cdecl([import|export])

after keeping these in mind the GSS server built as an console
app fairly easily


Wed Jan 29 20:59:20 EST 1997 Richard Basch
The build procedure has been fixed in the V1_0_WIN32_BRANCH.
However, the GSS client/server application bugs have not yet
been addressed.

The gss client appears to work with no other changes.
The dialog box actually expects:
host port service
eg. 2345

The fact that it merely prompts for a hostname is "broken".
The problem with the build procedure is that it did not use /GA,
and the use of the DLL line included /GD, which works similarly.