Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New release with the WPA2 fix #46

Closed
marcelstoer opened this issue Oct 17, 2017 · 19 comments

Comments

Projects
None yet
8 participants
@marcelstoer
Copy link
Contributor

commented Oct 17, 2017

Please create a new release at https://github.com/espressif/ESP8266_NONOS_SDK/releases which includes the WPA2 fix b762ea2. I guess that would mean releasing from the tip of master to include all 13 commits as per v2.1.0...master.

@jj2497

This comment has been minimized.

Copy link

commented Oct 21, 2017

It seems the fix results in reset wifi status. I can see the following messages periodically (I set ESP8266 to STATION mode only).

bcn_timout,ap_probe_send_start
ap_probe_send over, rest wifi status to disassoc
state: 5 -> 0 (1)
rm 0
pm close 7
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 8
cnt

connected with ssid-xxxxx, channel 8
dhcp client start...

If I revert back to SDK 2.1.0, it performs all right.

@marcelstoer

This comment has been minimized.

Copy link
Contributor Author

commented Oct 30, 2017

It's been nearly two weeks without any feedback. What's the status @espressif? I know that at least the NodeMCU project is waiting for a new release so we can ship a new release ourselves. Tagging @igrr as well.

@marcelstoer

This comment has been minimized.

Copy link
Contributor Author

commented Oct 31, 2017

I guess the question is why you are not releasing a 2.1.1 at https://github.com/espressif/ESP8266_NONOS_SDK/releases immediately which includes the KRACK fix? Why did you do this for ESP-IDF but not for this SDK?

@shinji2009

This comment has been minimized.

Copy link

commented Nov 2, 2017

sorry for spupid question i am not understand is crack fix already implemented on https://nodemcu-build.com/ if i download master ?

@marcelstoer

This comment has been minimized.

Copy link
Contributor Author

commented Nov 2, 2017

@shinji2009 Unfortunately not. First Espressif has to release a new SDK (that's what this issue is about) then we need to incorporate it into the NodeMCU firmware (nodemcu/nodemcu-firmware#2138) and release it.
-> we're all waiting for Espressif

@igrr

This comment has been minimized.

Copy link
Member

commented Nov 2, 2017

Unfortunately we are a bit constrained by QA resources at this point, with multiple SDK releases which need testing (IDF 2.1.1, IDF 3.0, ESP8266 SDKs, ...). We will try make the release as soon as possible.

@marcelstoer

This comment has been minimized.

Copy link
Contributor Author

commented Nov 2, 2017

Thank you Ivan, that's sounds more promising than the previous response from Espressif 😜

@wujiangang

This comment has been minimized.

Copy link
Contributor

commented Nov 3, 2017

hi, @marcelstoer please try branch release/v2.1.x, which added KRACK fix. v2.2.0 will be arranged to test soon.

@marcelstoer

This comment has been minimized.

Copy link
Contributor Author

commented Dec 30, 2017

Any updates on this? The whole reason why I was asking for an official 2.1.x release was that we (NodeMCU) can pull it in automatically. Our build scripts look for https://github.com/espressif/ESP8266_NONOS_SDK/archive/v$(SDK_FILE_VER).zip. Hence, if we had wanted to pull in the fix from the branch we'd have had to temporarily adjust the build scripts. In hind sight maybe we should have... Is there an ETA for 2.2?

@jcack-me

This comment has been minimized.

Copy link

commented Jan 3, 2018

We've also been patiently waiting on an official 2.2 release for several months.
An ETA will help our release planning and help us to manage customer expectations.
thanks

@FayeY

This comment has been minimized.

Copy link
Collaborator

commented Jan 3, 2018

Hi, so sorry for the late, we are working on the official V2.2 now, it will be released at the end of Jan. Sorry again for the inconvenience.

@jcack-me

This comment has been minimized.

Copy link

commented Jan 3, 2018

Many thanks, fingers crossed it doesn't slip!

@marcelstoer

This comment has been minimized.

Copy link
Contributor Author

commented Feb 5, 2018

fingers crossed it doesn't slip!

Pity it didn't help 😢

@jcack-me

This comment has been minimized.

Copy link

commented Feb 5, 2018

Hi FayeY,

The end of January has come and gone, and there is still no SDK release.
Do you have an update for us?

thanks

@jcack-me

This comment has been minimized.

Copy link

commented Feb 12, 2018

Another week goes by and still we are left waiting ... :(

@FayeY

This comment has been minimized.

Copy link
Collaborator

commented Feb 12, 2018

Hi, sorry that I thought there was a notification, the V2.2 has already been released on github Releases

@FayeY FayeY closed this Feb 12, 2018

@jcack-me

This comment has been minimized.

Copy link

commented Feb 12, 2018

Thanks.

@Code1110 Code1110 referenced this issue Feb 27, 2018

Merged

Update to sdk 2.2 #2269

3 of 4 tasks complete
@ESP-Geek

This comment has been minimized.

Copy link

commented Apr 12, 2018

@marcelstoer - Has this been integrated into the latest NodeMCU Build yet?
Many thanks all for your hard work!

@marcelstoer

This comment has been minimized.

Copy link
Contributor Author

commented Apr 12, 2018

Yep, https://github.com/nodemcu/nodemcu-firmware/releases. Follow NodeMCU on FB at https://www.facebook.com/NodeMCU/ and never miss an important announcement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.