> The names that NWAM uses come from the ESSID and BSSID of the AP, and > since the ESSID is a free-form string, and may well be "WEP-$uck$" in > some locations and "%%%yo%%%" in others, I think there's a problem > here, even for those who haven't yet stumbled over the space character > problem.
Ugh. That's a problem, but as per the issues I cited earlier, I'm not convinced that allowing the secobj value to be free-form is the right solution. -- meem _______________________________________________ networking-discuss mailing list [email protected]
