WIRE1x 1.1 beta release note [ Testing Environment ]: (a) EAP MD5: -Windows XP with Service Pack 2 -Windows Server 2003 Enterprise with Service Pack 1 (If you invoked the executable via "main.exe" and failed to authenticate, please execute "md5.exe" or "md5_NOP.exe" manually, where NOP stands for "non optimized version." We are still checking out the reason why it becomes malfunctioned after optimization.) (b) EAP PEAP: -Windows XP with Service Pack 2 -May malfunctioned on Windows Server 2003 Enterprise with Servic Pack 1 (If peap.exe cannot work properly, please execute peap_NOP.exe manually, where NOP stands for "non optimized version." We are still checking out the reason why it becomes malfunctioned after optimization.) (c) EAP TLS: -Windows XP with Service Pack 2 -May malfunctioned on Windows Server 2003 Enterprise with Servic Pack 1 (If tls.exe cannot work properly, please execute tls_NOP.exe manually, where NOP stands for "non optimized version." We are still checking out the reason why it becomes malfunctioned after optimization.) (d) EAP TTLS: -Windows XP with Service Pack 2 -May malfunctioned on Windows Server 2003 Enterprise with Servic Pack 1 (If tls.exe cannot work properly, please execute tls_NOP.exe manually, where NOP stands for "non optimized version." We are still checking out the reason why it becomes malfunctioned after optimization.) -We only tested authentications tunneled via PAP and MSCHAPv2 protocols; if you find that any other protocols work properly, we welcome and appreciate for your reporting. (e) main: We did not revise "main.exe" in this version. If you need the source code of "main.exe," please download from the previous version. [ About OS ]: Since our labaratory did not have enough various versions of Microsof Windows Operating Systems, if you find that any other versions work properly or not, we welcome and appreciate for your reporting. [ About WinPcap ]: NOTE that no matter which version of Windows you choice, you SHOULD install WinPcap 3.0; higher or lower versions may lead to some run time errors. ----------------------------------------------------------------------------------------------------- [ TLS NOTE ]: 1. If your client/server certification did not signed by a well-known Trusted Root CA, you MUST install the certification of the CA, which has signed your client/server certification, as a Trusted Root CA on your local computer. Otherwise, you may receive a unknown CA message. 2. Your client private key must save at the working directory of WIRE1x as the name "cert-clt.pem." Your Root CA certification must save at the working directory of WIRE1x as the name "root.pem." If there are still some problems, please try to install the client certification into the "Personal" cantainer on your local computer using "*.p12" format. [ TTLS, PEAP NOTE ]: 1. If your server certification did not signed by a well-known Trusted Root CA, you MUST install the certification of the CA, which has signed your server certification, as a Trusted Root CA on your local computer. Otherwise, you may receive a unknown CA message. ----------------------------------------------------------------------------------------------------- [ Bug Fixed List ]: EAP MD5: (1) Hard coded default athenticator's MAC address. (Chien-Chia Chen) (2) Code reformat. (Chien-Chia Chen) EAP PEAP: (1)Extract AAA server's MAC address from server reply frames. (Jui-Yi Chen) (2)Code reformat. (Chien-Chia Chen) EAP TLS: (1)Read several client or server certifications. (Jui-Yi Chen) (2)Extract AAA server's MAC address from server reply frames. (Jui-Yi Chen) (3)Code reformat. (Chien-Chia Chen) (4)Fix using external pointer reference to a local variable. (Guann-Long Chiou) EAP TTLS: (1)Extract AAA server's MAC address from server reply frames. (Jui-Yi Chen) (2)Code reformat. (Chien-Chia Chen) ----------------------------------------------------------------------------------------------------- Copyright 2002-2005 (C) WIRE Lab., National Tsing Hua University, Taiwan, R.O.C. WIRE1x Working Group 2006.04.14