[32559] in Kerberos
Re: Determing Kerberos version programatically
daemon@ATHENA.MIT.EDU (Marcus Watts)
Wed Aug 11 11:34:24 2010
to: kerberos@mit.edu
In-reply-to: <4C61CB92.6080405@globe.gov>
Date: Wed, 11 Aug 2010 11:34:17 -0400
From: Marcus Watts <mdw@umich.edu>
Message-Id: <E1OjDJp-0003AG-GZ@bruson.ifs.umich.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
Daniel Berger <dberger@globe.gov> writes:
> Date: Tue, 10 Aug 2010 15:58:42 MDT
> To: kerberos@mit.edu
> From: Daniel Berger <dberger@globe.gov>
> Subject: Determing Kerberos version programatically
>
> Hi,
>
> If I'm writing a Kerberos wrapper (a C extension), what's the best way
> to determine which version of the Kerberos library that I'm using?
>
> I see KADM5_API_VERSION_x, but I don't see anything that tells me I'm
> using, say 1.8.2, for example.
>
> Is there a way?
>
> Regards,
>
> Dan
Is there a *reason* you need to know if you're using 1.8.2 instead of
1.8.1 or 1.8.3? Generally speaking, you want these things to go by
feature not by release number. For features which are either add-on
patches, or configured at build time, this is particularly important.
Also keep in mind the sun and macintosh versions are yet again different.
The other twist to be very careful of is that since this is client/server,
just because your *client* code is 1.8.2, doesn't mean the *server*
is 1.8.2. The wire protocol does have a number, and there are provisions
in the protocol that are intended to hide some wire differences.
-Marcus Watts
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
