[16974] in Kerberos_V5_Development
Re: What is the intended calling convention on Windows between GSS
daemon@ATHENA.MIT.EDU (Jeffrey Altman)
Wed Jul 6 17:52:10 2011
X-Envelope-From: jaltman@secure-endpoints.com
X-MDaemon-Deliver-To: krbdev@mit.edu
Message-ID: <4E14D8FF.2040300@secure-endpoints.com>
Date: Wed, 06 Jul 2011 17:51:59 -0400
From: Jeffrey Altman <jaltman@secure-endpoints.com>
MIME-Version: 1.0
To: hartmans@painless-security.com
In-Reply-To: <tslhb7tpwzb.fsf@mit.edu>
Cc: krbdev@mit.edu
Reply-To: jaltman@secure-endpoints.com
Content-Type: multipart/mixed; boundary="===============2093951083=="
Errors-To: krbdev-bounces@mit.edu
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============2093951083==
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="------------enig1EA3B7823D26D09047B17804"
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig1EA3B7823D26D09047B17804
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On 6/13/2011 11:33 AM, Sam Hartman wrote:
>=20
> Jeff and others providing GSS implementations on Windows, I have a
> question.
>=20
> There's some complexity surrounding GSS-API calling conventions on
> Windows.
>=20
> It's my understanding that for gssapi_32.dll, MIt has traditionally use=
d
> the win32 (or whatever the non-C calling convention is called) for the
> exported symbols.
I was not involved in the original decision to select __stdcall for
GSSAPI on Windows. However, considering that if Microsoft was ever to
publish a GSSAPI DLL of their own it would be __stdcall I believe the
decision was the correct one.
In the work to bring Heimdal to Windows a decision was made to provide
compatibility with MIT and as such it uses __stdcall. It is my believe
that any application that is built against one gssapi dll should work
with any of the others.
I would prefer that any mechanism interfaces on Windows also make use of
__stdcall for the reasons you mention.
Jeffrey Altman
--------------enig1EA3B7823D26D09047B17804
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
iQEcBAEBAgAGBQJOFNkBAAoJENxm1CNJffh4Q/sH+wbsGC7P82w2gCm3Tfdktsu4
0We4ND0hQvZcGiGoywI2+W21G+zTfJB0YQi8u8AZv9tdJu4cPzSsDOc7EJ/Ezvmw
Kn7aIXexfcQf0rhpAR6Y2ozJOOOVrNegzux99ORVUZfl64qK5CWM59JoKH8AyECF
ttDWJcy5DAtzyz1RzjuLInml9fva4FvHIrxojIiYK7MkO6kgNYJKI8GdrGUOAfg9
uZ8iwSUF0sB43fjGw471l5fHGpDLjW/Gk77RhSLugED+9vERYoxrnLiRzkI9mbiW
HhzSnXuWzV5UVBs7G7/jBO2yKiEoShrr8WfB30eAfjZzQaIoNPubBcJhJnMcIs0=
=ESK5
-----END PGP SIGNATURE-----
--------------enig1EA3B7823D26D09047B17804--
--===============2093951083==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
--===============2093951083==--
