[PATCH] WPS: Fix hostapd PBC with Windows 7 supplicant

[Masashi Honma]

1) I should clarify the aim of my patch.
 - This is a pacth for hostapd.
 - This patch make hostapd to be connectable by Windows 7 supplicant
   with WPS PBC.
 - My patch changes a process of AP in Enrollee mode but this is not
   a patch for AP in Enrollee mode. This is because broken Windows
   supplicant requires M1 message.

2) I have gotten new test plan.
I have used very old Wi-Fi test plan v 1.6. Now, I have a newest one
v 2.0.3. The v 2.0.3's test 4.1.1 says "check M2 message". Thus, now
my patch does not affect the test because my patch changes only M1
message. And 4.1.2 checks only config methods attribute of probe
response, not M1. So, my patch doesn't affect to Wi-Fi certification.

> but it is strictly against the WPS specification
> and would make the AP fail some certification tests.

Which test do you mean ? I found an Wi-Fi certified AP which sends
M1 message same as my patch. The AP which can connect to Windows 7
supplicant with WPS PBC. The AP is CG-WLR300NM. The AP's Config
Methods attribute (0x1008) in M1 message enables PushButton method
same as my patch.

Regards,
Masashi Honma.


2011/4/18 Masashi Honma <masashi.honma at gmail.com>

> > but it is strictly against the WPS specification and would make the
> > AP fail some certification tests.
>
> I see. The test 4.1.1. requires config method without PBC.
>
>
> > What kind of use cases would this AP be used for?
>
> I expected connection of AP+Registrar (i.e. without external Registrar) and
> Enrollee (Enrollee is just STA, not AP). The AP has only PBC method
> because it is a headless device. The physical device of the AP has only a
> push
> button and some LEDs.
>
> I will try to find out better way.
>
> Regards,
> Masashi Honma.
>
>
> 2011/4/16 Jouni Malinen <j at w1.fi>
>
>> On Tue, Apr 12, 2011 at 12:00:09PM +0900, Masashi Honma wrote:
>> > The Windows 7 has it's own supplicant (not wpa_supplicant). If I
>> > configured the hostapd as only WPS PBC capable AP (i.e.
>> > "config_methods=push_button" in hostapd.conf), the Windows 7
>> > supplicant could not connect to the hostapd. Because the Windows 7
>> > supplicant popped up PIN input dialog.
>> >
>> > The attached patch solves this issue.
>>
>> Well, it may work around a completely broken WPS discovery mechanism in
>> Windows, but it is strictly against the WPS specification and would make
>> the AP fail some certification tests. Then again, support of PIN method
>> is mandatory in those tests, too. What kind of use cases would this AP
>> be used for? Only to work as a Registrar and only allow use of PBC to
>> connect Enrollees to the network? I.e., no support for use of PIN from
>> a label or for entering an Enrollee PIN.
>>
>> --
>> Jouni Malinen                                            PGP id EFC895FA
>> _______________________________________________
>> HostAP mailing list
>> HostAP at lists.shmoo.com
>> http://lists.shmoo.com/mailman/listinfo/hostap
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20110425/c611397c/attachment.htm