Kel Modderman | 1 Oct 2008 03:42
Picon
Favicon

[PATCH 1/2] wpa_gui-qt4: clean up closeEvent handler

When the system tray icon is created, qApp's setQuitOnLastWindowClosed
property is set to false, therefore do _not_ ignore widget close events, or
else wpa_gui will refuse to exit when the window manager is logging out.

While at it, remove WpaGui::fileExit() and connect fileExitAction to close().

Signed-off-by: Kel Modderman <kel <at> otaku42.de>
---
--- a/wpa_supplicant/wpa_gui-qt4/wpagui.cpp
+++ b/wpa_supplicant/wpa_gui-qt4/wpagui.cpp
 <at>  <at>  -37,7 +37,7  <at>  <at> 
 		SLOT(eventHistory()));
 	connect(fileSaveConfigAction, SIGNAL(triggered()), this,
 		SLOT(saveConfig()));
-	connect(fileExitAction, SIGNAL(triggered()), this, SLOT(fileExit()));
+	connect(fileExitAction, SIGNAL(triggered()), qApp, SLOT(quit()));
 	connect(networkAddAction, SIGNAL(triggered()), this,
 		SLOT(addNetwork()));
 	connect(networkEditAction, SIGNAL(triggered()), this,
 <at>  <at>  -1214,11 +1222,6  <at>  <at> 
 		showTrayMessage(QSystemTrayIcon::Information, 10, msg);
 }

-void WpaGui::fileExit()
-{
-	qApp->quit();
-}
-

 void WpaGui::closeEvent(QCloseEvent *event)
(Continue reading)

Kel Modderman | 1 Oct 2008 03:44
Picon
Favicon

[PATCH 2/2] wpa_gui-qt4: add support for starting in system tray only

Allow application to be started in the system tray only when started with
the `-t' command line argument.

Signed-off-by: Kel Modderman <kel <at> otaku42.de>
---
--- a/wpa_supplicant/wpa_gui-qt4/wpagui.cpp
+++ b/wpa_supplicant/wpa_gui-qt4/wpagui.cpp
 <at>  <at>  -80,17 +80,20  <at>  <at> 
 	scanres = NULL;
 	udr = NULL;
 	tray_icon = NULL;
+	startInTray = false;
 	ctrl_iface = NULL;
 	ctrl_conn = NULL;
 	monitor_conn = NULL;
 	msgNotifier = NULL;
 	ctrl_iface_dir = strdup("/var/run/wpa_supplicant");

-	if (QSystemTrayIcon::isSystemTrayAvailable())
-		createTrayIcon();
-
 	parse_argv();

+	if (QSystemTrayIcon::isSystemTrayAvailable())
+		createTrayIcon(startInTray);
+	else
+		show();
+
 	textStatus->setText("connecting to wpa_supplicant");
 	timer = new QTimer(this);
(Continue reading)

Kel Modderman | 1 Oct 2008 04:07
Picon
Favicon

Re: [PATCH 1/2] wpa_gui-qt4: clean up closeEvent handler

On Wednesday 01 October 2008 11:42:43 Kel Modderman wrote:
> While at it, remove WpaGui::fileExit() and connect fileExitAction to close().

s/close()/quit()/

Kel.
Tomonari Yoshimura | 1 Oct 2008 06:37
Picon

RE: Does wpa supplicant version 0.6.4 support Windows Server 2008NAP IEEE802.1X Enforcement ?

Thank you for your assistance.

The debug log messages of wap supplicant with our debug messages (### TEST9 ###) are shown below.
If you find any issues, could you please let us know ?
Could you send us the debug log messages you tested wpa supplicant with Windows XP SP3,
if possible ?

(1) Receiving SoH Request from Server (Windows Server 2008).
### TEST9 ### : SoH Request Received from Server.
EAP-PEAP: Decrypted Phase 2 EAP - hexdump(len=20): fe 00 01 37 00 00 00 21 00 07 00 08 00 00 01 37 00 02 00 00

(2) SoH TLV is generated and sent back to Server.
### TEST9 ### SoH TLV is generated. (we use dummy correlationId)
EAP-PEAP: Encrypting Phase 2 data - hexdump(len=113): 02 08 00 71 fe 00 01 37 00 00 00 21 00 07 00 61 00 00 01 37 00
01 00 59 00 07
00 55 00 00 01 37 00 02 00 4d 00 07 00 1e 00 00 01 37 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 01 00
00 02 00 04 00 01 37 00 00 07 00 1f 00 00 01 37 03 11 06 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02

(3) Server sends EAP Authentication failure as a response. 
RX EAPOL - hexdump(len=46): 01 00 00 04 04 00 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00
00 00 00 00 00 00 00 00 00 00 00
EAP: Received EAP-Failure
CTRL-EVENT-EAP-FAILURE EAP authentication failed

Windows Server 2008 NPS event log shows 
 ReasonCode  300
 Reason: No authentication information available in the Security Package.

We checked  tncc_build_soh() in src/eap_peer/tncc.c and Microsoft specifications
(Continue reading)

Jouni Malinen | 1 Oct 2008 08:49
Picon

Re: [PATCH 1/2] wpa_gui-qt4: clean up closeEvent handler

On Wed, Oct 01, 2008 at 11:42:43AM +1000, Kel Modderman wrote:
> When the system tray icon is created, qApp's setQuitOnLastWindowClosed
> property is set to false, therefore do _not_ ignore widget close events, or
> else wpa_gui will refuse to exit when the window manager is logging out.

Thanks, applied (with fixed commit message). In addition, I applied the
start-in-tray-only patch (2/2).

--

-- 
Jouni Malinen                                            PGP id EFC895FA
Jouni Malinen | 1 Oct 2008 09:05
Picon

Re: Does wpa supplicant version 0.6.4 support Windows Server 2008NAP IEEE802.1X Enforcement ?

On Wed, Oct 01, 2008 at 01:37:24PM +0900, Tomonari Yoshimura wrote:

> The debug log messages of wap supplicant with our debug messages (### TEST9 ###) are shown below.

Thanks!

> Could you send us the debug log messages you tested wpa supplicant with Windows XP SP3,
> if possible ?

The test I did was using Windows XP SP3 with its supplicant against
hostapd (as a EAP-PEAP server with NAP enabled). I've included the SoH
TLV data that the Microsoft code sent in the end of this message. It
could help in figuring out which values are needed for Windows Server
2008 to accept the SoH TLV.

> (2) SoH TLV is generated and sent back to Server.
> ### TEST9 ### SoH TLV is generated. (we use dummy correlationId)

> Windows Server 2008 NPS event log shows 
>  ReasonCode  300
>  Reason: No authentication information available in the Security Package.

I've no idea what this means..

> We checked  tncc_build_soh() in src/eap_peer/tncc.c and Microsoft specifications
> [MS-PEAP] and [MS-SOH], but we cannot find the cause of the error.

Did you add the field marked with TODO? If I remember correctly, some of
them were marked as mandatory in the specification. As a quick test,
you could just copy the data from the SoH example below for
(Continue reading)

David Ehrmann | 1 Oct 2008 20:11
Picon

wpa_supplicant can't reauthenticate without resetting the driver (driver bug?)

I think this is a driver bug (ndiswrapper), but I'm checking here, first.

I see this block in the log, repeated basically every second.  I don't
see any actual errors, it just looks like the authentication never
completes, but the driver tells wpa_supplicant that it should
authenticate before any timeout occurs.

Thanks in advance.

RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c07 len=92
AssocReq IE wireless event - hexdump(len=84): 00 10 47 6f 6f 67 6c 65
57 69 46 69 53 65 63 75 72 65 01 04 02 04 0b 16 30 26 01 00 00 0f ac
02 01 00 00 0f ac 04 01 00 00 0f ac 01 00 00 01 00 5b 77 fd dc 8e a9
6d 22 fb 78 49 36 3e a2 1f 8c dd 09 00 03 7f 01 01 00 00 00 00 dd 07
00 50 f2 02 00 01 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c08 len=48
AssocResp IE wireless event - hexdump(len=40): 01 04 82 84 0b 16 07 06
55 53 20 01 0b 1b dd 18 00 50 f2 02 01 01 81 00 03 a4 00 00 27 a4 00
00 42 43 5e 00 62 32 2f 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0d:xx:xx:xx:xx
Association info event
req_ies - hexdump(len=84): 00 10 47 6f 6f 67 6c 65 57 69 46 69 53 65
63 75 72 65 01 04 02 04 0b 16 30 26 01 00 00 0f ac 02 01 00 00 0f ac
04 01 00 00 0f ac 01 00 00 01 00 5b 77 fd dc 8e a9 6d 22 fb 78 49 36
3e a2 1f 8c dd 09 00 03 7f 01 01 00 00 00 00 dd 07 00 50 f2 02 00 01
00
(Continue reading)

David Ehrmann | 1 Oct 2008 23:28
Picon

Re: wpa_supplicant can't reauthenticate without resetting the driver (driver bug?)

I forgot to mention, this is with wpa_supplicant 0.6.3.

On Wed, Oct 1, 2008 at 11:11 AM, David Ehrmann <ehrmann <at> gmail.com> wrote:
> I think this is a driver bug (ndiswrapper), but I'm checking here, first.
>
> I see this block in the log, repeated basically every second.  I don't
> see any actual errors, it just looks like the authentication never
> completes, but the driver tells wpa_supplicant that it should
> authenticate before any timeout occurs.
>
> Thanks in advance.
>
> RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
> Wireless event: cmd=0x8c07 len=92
> AssocReq IE wireless event - hexdump(len=84): 00 10 47 6f 6f 67 6c 65
> 57 69 46 69 53 65 63 75 72 65 01 04 02 04 0b 16 30 26 01 00 00 0f ac
> 02 01 00 00 0f ac 04 01 00 00 0f ac 01 00 00 01 00 5b 77 fd dc 8e a9
> 6d 22 fb 78 49 36 3e a2 1f 8c dd 09 00 03 7f 01 01 00 00 00 00 dd 07
> 00 50 f2 02 00 01 00
> RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
> Wireless event: cmd=0x8c08 len=48
> AssocResp IE wireless event - hexdump(len=40): 01 04 82 84 0b 16 07 06
> 55 53 20 01 0b 1b dd 18 00 50 f2 02 01 01 81 00 03 a4 00 00 27 a4 00
> 00 42 43 5e 00 62 32 2f 00
> RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:0d:xx:xx:xx:xx
> Association info event
> req_ies - hexdump(len=84): 00 10 47 6f 6f 67 6c 65 57 69 46 69 53 65
> 63 75 72 65 01 04 02 04 0b 16 30 26 01 00 00 0f ac 02 01 00 00 0f ac
(Continue reading)

James Woo | 2 Oct 2008 01:39

Re: HostAP Digest, Vol 66, Issue 2

hostap-request <at> lists.shmoo.com wrote:
> ----------------------------------------------------------------------
>
> Message: 2
> Date: Wed, 1 Oct 2008 10:05:06 +0300
> From: Jouni Malinen <j <at> w1.fi>
> Subject: Re: Does wpa supplicant version 0.6.4 support Windows Server
> 	2008NAP IEEE802.1X Enforcement ?
> To: hostap <at> lists.shmoo.com
> Message-ID: <20081001070506.GN4853 <at> jm.kir.nu>
> Content-Type: text/plain; charset=utf-8
>   
> EAP-PEAP: SoH TLV - hexdump(len=418):
> SoH Header packet:
>   Outer Type: 00 07 (7)
>   Length: 01 9e
>   IANA SMI Code: 00 00 01 37
>   Inner Type: 00 02 (version 2 - Value: SoH Mode Sub-Header | SSoH |
> SoHReportEntry(0+))
>   Inner Length: 01 96
>   Value:
> SoH Mode Sub-Header:
>   Outer Type: 00 07 (7)
>   Length: 00 1e
>   IANA SMI Code: 00 00 01 37
>   Value:
>     Correlation ID: 6f a0 2d f4 d8 51 4e 00 bb 76 28 c4 8a e5 1d f1 01 c8 8d 8e f9 1f a1 32 (== MS-CorrelationId)
>     Intent Flag: 01 (SoH request message)
>     Content-Type Flag: 00
>   
(Continue reading)

Tomonari Yoshimura | 2 Oct 2008 05:09
Picon

RE: Does wpa supplicant version 0.6.4 support Windows Server2008NAP IEEE802.1X Enforcement ?


>Did you add the field marked with TODO? If I remember correctly, some of them were marked as mandatory in the 
>specification. As a quick test, you could just copy the data from the SoH example below for
MS-Machine-Inventory, 
>MS-Quarantine-State, and MS-MachineName. It would be interesting to see whether that is all that is
needed to get
>the server accepting the message.
Thank you for your assistance.

I tested using the SoH example that is shown in the previous mail.
The EAP authentication completes successfully,
however the following messages are received from Server 2008,
EAP-TLV: Unsupported TLV Type 7
EAP-TLV: Unsupported TLV Type 12
I suppose TLV Type7 and 12 are not mandatory for NAP authentication, so these are ignored.

------------------------------------------------------------------------------------------------------------------------------------
-----------------------------
### NAP experiment ### SoH Setting
EAP-PEAP: Phase 2 Request: Nak type=254
EAP-PEAP: Allowed Phase2 EAP types - hexdump(len=1): 1a
EAP-PEAP: Encrypting Phase 2 data - hexdump(len=442): 02 07 01 ba fe 00 01 37 00 00 00 21 00 07 01 aa 00 00 01 37 00
01 01 a2 00 07
01 9e 00 00 01 37 00 02 01 96 00 07 00 1e 00 00 01 37 6f a0 2d f4 d8 51 4e 00 bb 76 28 c4 8a e5 1d f1 01 c8 8d 8e f9 1f a1 32 01 00
00 02 00 04 00 01 37 00 00 07 00 4f 00 00 01 37 03 11 01 00 00 00 05 00 00 00 01 00 00 0a 28 00 03 00 00 00 00 05 00 06 4a 6f 75 6e
69 00 06 6f a0 2d f4 d8 51 4e 00 bb 76 28 c4 8a e5 1d f1 01 c8 8d 8e f9 1f a1 32 02 00 09 ff ff ff ff ff ff ff ff 00 01 00 08 de ca
fb ad 01 00 02 00 04 00 01 37 80 00 07 00 08 00 01 37 80 02 00 00 00 00 07 00 08 00 01 37 80 00 00 01 05 00 08 00 01 00 00 0a 00 40
4e 00 6f 00 72 00 74 00 6f 00 6e 00 20 00 49 00 6e 00 74 00 65 00 72 00 6e 00 65 00 74 00 20 00 57 00 6f 00 72 00 6d 00 20 00 50 00
72 00 6f 00 74 00 65 00 63 00 74 00 69 00 6f 00 6e 00 00 00 00 0b 00 04 00 00 00 01 00 0a 00 24 4d 00 49 00 43 00 52 00 4f 00 53 00
4f 00 46 00 54 00 20 00 50 00 52 00 4f 00 44 00 55 00 43 00 54 00 00 00 00 0b 00 04 00 00 00 04 00 08 00 01 01 00 0a 00 2c 4e 00 6f
(Continue reading)


Gmane