Peter Memishian writes: > > > 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.
Yep; I agree on that. I'm just pointing out that the NWAM prototype didn't take this into consideration, it was deployed like that via OpenSolaris, and we weren't forced into seeing the problem until too late. Either totally breaking it with a simple hash or just eliding (rather than translating to '.') the non-alphabetic illegal characters makes more sense to me. (Eliding seems better to me than translating, because the dladm strings are so darned short, and truncation here is ugly -- it typically chops off the end of the BSSID, which is where all the variance is, and we do see collisions.) -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
