Re: [Perlgssapi-users] Client/Server Question

[Achim G. <ac...@gr...>]

>  Should the client/server pair work properly? Is there anyone
> that might have an idea why its also coring?

1. SSPI is the Win32 API to Windows Authentication system.
SSPI is able to deal with the GSSAPI protocol, Kerberos5 over GSSAPI
(the protocol) for example.

GSSAPI.pm is not an interface to SSPI.
GSSAPI.pm is an interface to GSSAPI (the C-interface, RFC 2744).

Maybe in future I am going to write a Perl-Wrapper to Win32-API SSPI
to make Perlskripts on Windows use the SSPI directly.

As a workaround you can build GSSAPI.pm against MIT Kerberos for Windows.

2. Can you use the versions from Subversion repository

http://sourceforge.net/projects/perlgssapi/

(I've added workarounds to the client/server scripts).

3. GSSAPI.pm has a bug (I have added it). to avoid you
can use a quick workaround and change all lines of type

my $out_mech,

to 

undef

in your code.

example:



        my $status = GSSAPI::Context::accept(
                        $server_context,
                        GSS_C_NO_CREDENTIAL,
                        $gss_input_token,
                        GSS_C_NO_CHANNEL_BINDINGS,
                        my $gss_client_name,
                        undef,
                        my $gss_output_token,
                        my $out_flags,
                        my $out_time,
                        my $gss_delegated_cred);

Let me know what happens then an let me know the output.

Achim