appropriately (<host> is the name of the host running the server,
not the RADIUS server).
-% gss-client -port 5555 -spnego -mech "{1 3 6 1 4 1 5322 22 1 18}" \
+% gss-client -port 5555 -spnego -mech "{1 3 6 1 5 5 15 1 1 18}" \
-user <user>@<realm> -pass <pass> <host> host@<host> \
"Testing GSS EAP"
% gss-server -port 5555 -export host@<host>
For the client, the GSS EAP mechanism can be specified on the command line:
-smbclient --password samba --mechanism 1.3.6.1.4.1.5322.22.1.18 '\\host\share'".
+smbclient --password samba --mechanism 1.3.6.1.5.5.15.1.1.18 '\\host\share'".
There is no Moonshot SSPI implementation as yet, so it is not possible to test
with a Windows client.
# Any encryption type supported by Kerberos can be defined as the
# last element of the OID arc.
#
-eap-aes128 1.3.6.1.4.1.5322.22.1.17 mech_eap.so
-eap-aes256 1.3.6.1.4.1.5322.22.1.18 mech_eap.so
+eap-aes128 1.3.6.1.5.5.15.1.1.17 mech_eap.so
+eap-aes256 1.3.6.1.5.5.15.1.1.18 mech_eap.so
#include "gssapiP_eap.h"
static gss_OID_desc gssEapNtEapName = {
- /* 1.3.6.1.4.1.5322.22.2.1 */
+ /* 1.3.6.1.5.5.15.2.1 */
8, "\x2B\x06\x01\x05\x05\x0f\x02\x01"
};