WPA2 max-length hex passwords are not supported

[ElectronicWar]

After poking around in the softap-setup Javascript I assume that the provided WiFi password is always hex-encoded before sending it to the setup API.

Line 39405 in softap-browser.js
securePass = this.__publicKey.encrypt(opts.password, 'hex');

I am, however, using a 256 bit (64 characters) hex-key as my WiFi password.
This is within specification and the password needs to be passed on directly without further encoding in order to work.

This was already an issue with Linux where the WiFi setup GUI does not support it and I had to edit config files directly for it to work.

[digistump]

The encoding should not be an issue - if you send FFFFFF it will get encrypted and then hex encoded, and then decoded and then decrypted on the Oak and saved as FFFFFF.

What is the behavior that you are seeing when you try to use your password? Is the WiFi wizard setup failing and giving an error? Or does it succeed but your Oak doesn't ever connect to you WiFi?

[ElectronicWar]

It fails to connect over and over (tried multiple times). I will be able to provide more testing by tomorrow with my setup and will also try to use a guest network with a "standard" password to see it that works. Serial logging will be provided as well.

I have used my phone's hotspot in the meantime successfully so I think it's something related to my network and no general problem with my Oaks.

[digistump]

Thanks for the details - let me know how the testing goes, happy to try to
chase this down, but a quick look at the relevant code didn't show any
obvious issues with a password like you describe.

Thanks,
Erik

On Thu, May 19, 2016 at 1:19 AM, Manuel [email protected] wrote:

It fails to connect over and over (tried multiple times). I will be able
to provide more testing by tomorrow with my setup and will also try to use
a guest network with a "standard" password to see it that works. Serial
logging will be provided as well.

I have used my phone's hotspot in the meantime successfully so I think
it's something related to my network and no general problem with my Oaks.

—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
#6 (comment)