[kde-linux] SPNEGO Fails for Konqueror

[Mike Thrift]

Thank you so much for your reply!  Yes I did mean smb:// sorry about 
that.  I have searched bugs.kde.org, and will do again.  When I come 
back I will put together a more detailed account of what I've done, and 
what I can see on my end.  I've also heard about bugs in krb, I'll see 
if I find anything further. Thanks again for the feedback!

Mike.

Kevin Krammer wrote:

>On Wednesday 02 November 2005 16:16, Mike Thrift wrote:
>  
>
>>Hi,
>>    I've asked this question in a number of locations, and I've seen
>>many instances of a similar problem, most of these instances go
>>unanswered.  I have asked this question in various ways, after
>>researching more each time, and I have yet to get an answer.  Googling
>>list archives such as samba's archives, kde's archives, and others, have
>>revealed no fixes for this problem.
>>    My setup is a FC4 box setup on a Win2003 Active Directory Domain.  I
>>can confirm my connection to the domain, and I authenticate without
>>problems to the domain.  Running a klist shows my current tickets, and
>>issuing the command: smbclient //xyz/abc -k drops me into the share I
>>request without hesitation.  Yet, for some reason, attempting to access
>>the same share through KDE using: konqueror //xyz/abc prompts me for a
>>password, and leaves the following in my .xsession-errors:
>>    
>>
>
>Did you mean using a smb:// URI in Konqueror?
>
>  
>
>>I have noticed that smbclient will only drop me into the share when I
>>issue the -k flag, and doesn't assume kerberos auth by default, maybe
>>that's the problem in KDE?  Does anybody have any idea why this wouldn't
>>work?  What I've read concerning NTLM, spnego etc. is that it is all
>>enabled by default, and it's clear that my system is attempting to
>>authenticate, but something just isn't clicking.  Any help or
>>suggestions are greatly appreciated.  My software versions are:
>>    
>>
>
>It could be a bug in the Kerberos implementation or the code using it.
>I remember reading about such a problem but I think it has been fixed already. 
>Maybe it isn't in 3.4 yet, just in 3.5 (but as it is a fix it think it should 
>be in 3.4 as well)
>
>Could you check on bugs.kde.org if you find anything related and if not, maybe 
>post all the information you have gathered into a new report?
>
>Cheers,
>Kevin
>
>  
>
>------------------------------------------------------------------------
>
>___________________________________________________
>This message is from the kde-linux mailing list.
>Account management:  https://mail.kde.org/mailman/listinfo/kde-linux.
>Archives: http://lists.kde.org/.
>More info: http://www.kde.org/faq.html.
>