'Contagious' wi-fi virus created by Liverpool researchers
bbc.co.uk
bbc.co.uk
That is the wrong approach. User education is hard, and lacks incentives for the gear makers, but adding new layers (maybe proprietary, maybe with vulnerabilities of their own) is the wrong approach. The autoconfiguration features on some routers are an example.
Equally bad is the "dumbing down" imperative that in recent years has made interfaces more opaque, restrictive and stupid. "Click this big, colorful icon and we'll do it all for you, so you don't have to think!" -- and then interface makers try to cope with users being more ignorant than ever -- failing to perceive the cause and effect relationship.
The right approach is giving controls for all the functionality, status displays to show what is happening, explaining in plain terms what each control is for, giving step by step instructions for the essentials, and making the default configuration safe. (In the case of a router, this would mean no WAN connection until you configure the device.)
https://wikidevi.com/wiki/Xmlset_roodkcableoj28840ybtide https://github.com/elvanderb/TCP-32764
Conceptually, device bonding seems like the right way for consumers but WPS doesn't do it very well.
Source: 2 years ago I spoke at Blackhat EU on breaking into MiFi hotspots[1] and I've been breaking Linux-based hardware devices since about 2011.
Technically correct, the best kind of correct.
Here's the link to the research, which is primarily concerned with methods of detecting AP-AP viruses, the actual Chameleon virus seems to be just some kind of proxy to test spread and detection of real viruses.