PineAP limitations?

[comatose603]

Do clients have to be associated with open/non-encrypted APs in order for PineAP to grab the association? And is there a way to circumvent this limitation?

[Skinny]

The AP you spoof with the pineapple must be an open AP in order to get a device to connect. Spoofing an AP that is encrypted will not work because during the 4-way handshake authentication process, the client will find out that you are not the AP you say that you are. I am not aware of a way to circumvent this limitation.

[comatose603]

Understood. Figured I'd ask. Was wondering if I should, perhaps, set my PineAP to have the same MAC as a target AP. And/or if there was a way to stetup PineAP with a blank WPS or WPA key that a user might just click through. ...? For instance, "Please enter WPA," <DERP>, <clicks OK with blank key>, Associated to PineAP.

[barry99705]

On 7/28/2016 at 11:43 AM, comatose603 said:

Understood. Figured I'd ask. Was wondering if I should, perhaps, set my PineAP to have the same MAC as a target AP. And/or if there was a way to stetup PineAP with a blank WPS or WPA key that a user might just click through. ...? For instance, "Please enter WPA," <DERP>, <clicks OK with blank key>, Associated to PineAP.

I have never seen any client do this.  Pretty sure even the noobest user would think twice about that one.

[Sebkinne]

On 7/28/2016 at 8:43 AM, comatose603 said:

Understood. Figured I'd ask. Was wondering if I should, perhaps, set my PineAP to have the same MAC as a target AP. And/or if there was a way to stetup PineAP with a blank WPS or WPA key that a user might just click through. ...? For instance, "Please enter WPA," <DERP>, <clicks OK with blank key>, Associated to PineAP.

Not possible, sorry. WPA keys need to be 8 characters long.