Re: Help : Can not contact KDC

Try authenticating (i.e entering your username and password) with the firewall instead of stopping it. - Priya Abhishek Rahirikar <[EMAIL PROTECTED]> 02/11/2008 07:25 PM Please respond to [EMAIL PROTECTED] To Priya Govindarajan/Lenexa/[EMAIL PROTECTED] cc Kerberos Subject Re: Help

Interoperability between Linux KDC - Windows client

Hi, I have some questions on interoperbility while kerberizing an application to provide Single Sign On support. Currently implementation uses GssAPI for linux kdc/server in linux/client in Linux and SSPI for Windows AD/ server on windows/client on windows. I am trying the following interopera

Question on security of keytab file.

Hi, I understand that the keytab file contains the secret key associated with the server principal. The question is while providing support for a service to be a kerberized service - what are the security issues/advantages by providing the option for the user to have individual keytab file

what all does instance include in user principal name - username/[EMAIL PROTECTED]

Hi, I have been using user principal name as - [EMAIL PROTECTED] , usr1/[EMAIL PROTECTED], usr1/[EMAIL PROTECTED] In general, I understand that instance is the host name . What all does instance include here in user principal name ?. Any link to more information will be very helpful. Than

question on gss_acquire_cred

Hi, I am trying to understand how gss_acquire_cred works. When trying gss_server and gss_client - sample programs : When gss_server run as user root the gss_acquire_cred function executes without any errors. (The service principal key is added to the keytab file) When I execute gss_server