Slight source problems with Kerberos shipped with Tru64 UNIX

From: Nikola Milutinovic (Nikola.Milutinovic_at_ev.co.yu)
Date: 05/07/04

  • Next message: Jim Zimmerman: "vdump errors" 
    Date: Fri, 07 May 2004 13:02:35 +0200
To: Tru64 UNIX Managers <tru64-unix-managers@ornl.gov>

    Hi all.

    Tru64 UNIX 5.1B ships with CyberSafe's implementation of Kerberos V and
    GSSAPI, together with header/library files. It is included in OSFSSOW2K
    (OSF Single-Sign-On for Winodws 2000) subset of the "Associated products
    CD".

    While this is thrilling (CS implementation is thread-safe, unlike
    Heimdal and especially MIT), there was one slight, but unpleasant bug in
    the sources. There is a confusion in "platform" definition in
    "/usr/include/gssapi/compat.h". Line 153 reads:

    #if defined(__aix43) || defined(__linux) || defined(__tru64)

    while the defined CPP symbol should be "__digital" (at least other three
    lines use that symbol). After changing that to:

    #if defined(__aix43) || defined(__linux) || defined(__tru64) ||
    defined(__digital)

    Cyrus SASL 2.1.18 compiled. I should write to cyrus mailing list with an
    update to configure script for 5.1B.

    So, guys from DEC/Compaq/HP, take a look at this, please. It is a small
    show-stopper, but it should be corrected.

    BTW, why is CS Kerberos5/GSSAPI burried so deep? Why isn't it generally
    available? Why do I have to install OSFSSOW2K to get (a rather good, I'm
    told) implementation of Kerberos5? I think it should go into base subsets.

    Nix.

  • Next message: Jim Zimmerman: "vdump errors"