Discussion de forum
Résolu
KRACK VIRUS
Can you please tell me what Videotron is doing to ensure its clients are protected from the above vulnerability?
Hi GMoncalieri,
If you had legacy services with Videotron such as illico television and internet service or, if you are currently a Videotron mobile subscriber, you will be able to use the Customer Center. If you only have Helix services, only the My Helix Account section will be accessible to you.
So in principle, if you had services before migrating to Helix, the two accesses will be consolidated following this migration and yes, you would be able to log in the Customer Center with the same username and password as for Helix. In some cases, it is still possible that due to some system issue both legacy and Helix account were not merged and in this case, you may need to log in with different username and password.
As we cannot access your file or confirm information relating to it on the forum, we can only refer you to the technical support team so that verifications can be completed: http://www.videotron.com/residential/contact-us
1 Réponse
Hello thje,
It seems like Harkane provided information about the WPA2 Krack Flaw over here : Information for the WPA2 KRACK Flaw and Videotron's Zyxel router
According to Zyxel:
http://www.zyxel.com/support/announcement_wpa2_key_management.shtml
The only routers affected are those with the 802.11r Fast-BSS Transition (FT) handshake feature. Those are models NWA5301-NJ, NWA5123-AC, WAC6103D-I and WAC6500 series. If you have one of those models, you will have to wait for February 2018 for a fix. You can also turn off that feature (see link above) to prevent been affected by the flaw.
Videotron's latest router is actually Zyxel's EMG2926 and is not in the list.
Zyxel's position on this is that those models not included are not affected: "For products not listed, they are not affected to the attacks either because they are not designed to act as WiFi clients, do not support 802.11r Fast-BSS Transition handshake, or do not support peer-key handshake by default."
That should clear it up.
