Actually, our product doesn't require EAP-GSS, nor EAP-Kerberos. Instead, we use existing, popular authentication mechanisms to provide kerberos functionality to mainstream RADIUS servers. There is no additional software required other than the EAP supplicant, and the client doesn't even realize that they're authenticating to anything different.
Our product doesn't even need Kerberos for Windows in order to authenticate the client to the Kerberos Database. That being said, we do not currently have the capability to pass the ticket on to the client. Our software is simply for authenticating kerberos credentials against the server. Any other thoughts? Chris - - - - - - - - - - - - - - - - - - - - Christopher M. Hutchison, CEO NetSteady Communications, Ltd. P.O. Box 392 Galloway, Ohio 43119 Phone: 614-853-0091 Skype: wifi_chris Email: cmhutch [at] netsteady.cc http://www.netsteady.cc ________________________________________________ Kerberos mailing list [email protected] https://mailman.mit.edu/mailman/listinfo/kerberos
