I'm fairly certain that the GSI GSSAPI libraries do not have an equivalent to 
mechglue_internal_krb5_init or gss_mech_initialize. These functions are not 
part of the standard GSSAPI.

----- "Ricardo Rocha" <ricardo.ro...@cern.ch> wrote:
> I'm using version 0.1-4 (libgssglue0, coming with debian unstable),
> and i see in /etc/gssapi_mech.conf:
> 
> # NOTE:
> # The initiaiization function "mechglue_internal_krb5_init"
> # is used for the MIT krb5 gssapi mechanism.  This special
> # function name indicates that an internal function should
> # be used to determine the entry points for the MIT gssapi
> # mechanism funtions.
> #
> # library                               initialization function
> # ================================      ==========================
> # The MIT K5 gssapi library, use special function for initialization.
> #/usr/lib/libgssapi_krb5.so             mechglue_internal_krb5_init
> /usr/lib/libgssapi_krb5.so.2            mechglue_internal_krb5_init
> #
> # The SPKM3 gssapi library function.  Use the function
> spkm3_gss_initialize.
> # /usr/local/gss_mechs/spkm/spkm3/libgssapi_spkm3.so   
> spkm3_gss_initialize
> 
> It might be that passing the right initialization function i can just
> use the unpatched mechglue. I'll investigate a bit more, but if you
> have a guess for what this function could be...
> 
> Thank you very much,
>   Ricardo
> 
> On Wed, Apr 14, 2010 at 3:51 PM, Jim Basney <jbas...@ncsa.uiuc.edu>
> wrote:
> > Last time I looked into it, the original GSSAPI mechglue library
> required the underlying GSSAPI libraries to be "mechglue aware" (i.e.,
> have something like gss_mech_initialize). The patched version removes
> that requirement.
> >
> > ----- "Ricardo Rocha" <ricardo.ro...@cern.ch> wrote:
> >> Hi Jim.
> >>
> >> Thanks for the link.
> >>
> >> I had seen it in my searches, but i thought it was only needed for
> >> openssh gsi. I thought the mechglue library was accepting any
> gssapi
> >> plugin implementation, and that its purpose was exactly to load
> >> multiple mechanisms on the same machine. Why do i need a patched
> >> version to use the gsi plugin?
> >>
> >> Thanks again,
> >>   Ricardo
> >>
> >> On Wed, Apr 14, 2010 at 3:32 PM, Jim Basney
> <jbas...@ncsa.uiuc.edu>
> >> wrote:
> >> > Hi Ricardo,
> >> >
> >> > For a modified version of the gssapi-mechglue library that works
> >> with the GSI GSSAPI libraries, please see:
> >> > http://grid.ncsa.illinois.edu/gssapi-mechglue/
> >> > It includes a gss_initialize() function that does the
> >> initialization.
> >> >
> >> > -Jim
> >> >
> >> > ----- "Ricardo Rocha" <ricardo.ro...@cern.ch> wrote:
> >> >> Hi.
> >> >>
> >> >> (i've sent this same message yesterday, but i wasn't subscribed
> to
> >> the
> >> >> list)
> >> >>
> >> >> I'm trying to use the gssapi globus gsi plugin, via the gssglue
> >> >> (mechglue) libraries.
> >> >>
> >> >> I've configured gssapi_mech.conf with something similar to the
> >> >> default
> >> >> krb5 config:
> >> >> """
> >> >> # globus gsi
> >> >> /usr/lib/libglobus_gssapi_gsi.so.4
> >> >> """
> >> >>
> >> >> (i'm fetching the globus libraries from debian unstable)
> >> >>
> >> >> >From here i get the following error:
> >> >> """
> >> >> /usr/lib/libglobus_gssapi_gsi.so.4.3.0: undefined symbol:
> >> >> gss_mech_initialize: searching for symbol 'gss_mech_initialize'
> in
> >> >> '/usr/lib/libglobus_gssapi_gsi.so.4.3.0'
> >> >> """
> >> >>
> >> >> I've tried to specify the initialization function (as is done
> for
> >> >> krb5), but i don't know the name of the function that mechglue
> >> should
> >> >> be calling in the globus plugin (guessing around i keep getting
> >> >> segfaults).
> >> >>
> >> >> Can someone give me a hand with this? Or maybe point me to some
> >> docs
> >> >> (my google searches are giving nothing)?
> >> >>
> >> >> Thanks,
> >> >>  Ricardo
> >> >
> >

Reply via email to