Comment 1 for bug 1258496

My first instinct is just to use "{network name} ({encryption type})" whenever there's more than one network with the same name.

I wonder if we can do anything here to protect against social engineering attacks. I could camp outside a company office and set up a network with the same name but different encryption method. A device connecting automatically to the previous network would be safe. But a new employee, told to connect to "Yoyodyne" and confronted with a choice between "Yoyodyne (WPA2)" and "Yoyodyne (LEAP)", could easily try the wrong one -- and now I've captured the password to the company's real network. Has this problem been dealt with before?