Mobility XE Client 8.0 and EAP-MD5 Authentication
Technical Note 2231
Last Reviewed 27-Jun-2008
Applies to:
Mobility XE client version 8.0 only
Mobility client OS: all platforms
Printer-friendly versionSummary
As of Mobility XE version 8.0., NetMotion has begun deprecating EAP-MD5 as an authentication protocol. While EAP-MD5 is still available as a choice in the Authentication — Protocol server setting, by default the 8.0 Mobility XE client does not support it. This tech note explains how to configure an 8.0 client to support EAP-MD5.
Note: future releases of Mobility XE will not include any support for EAP-MD5. If you are currently using EAP-MD5, NetMotion strongly recommends implementing a more secure authentication protocol.
Configuring 8.0 clients for EAP-MD5 authentication
By default, the Mobility XE 8.0 client does not support EAP-MD5 authentication. However, you can configure a registry setting on the client device that enables support for this protocol. Note: if you are using Windows Mobile or Windows CE clients, you will need to use a third-party registry editor to add this setting.
To set the key for EAP-MD5 in devices running Windows 2000, Windows XP, or Windows Vista, download and run Win32_MD5.reg.
The key that will be added to the registry looks like this:
Registry key
|
Name
|
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetMotion\Mobility Client
|
Value
|
"HelloListMask"="0000006f"
|
To set the key for EAP-MD5 in devices running Windows Mobile or Windows CE, download and run WinCE_MD5.reg.
The key that will be added to the registry looks like this:
Registry key
|
Name
|
HKEY_LOCAL_MACHINE\Software\NetMotion\Mobility Client
|
Value
|
"HelloListMask"="0000006f"
|
Related Information
9979
|
NetMotion Mobility Technical Notes
|
Please comment on this technical note.
