I believe the problem lies in the intent of the service. It is 'common' knowledge that a certain open wireless cloud is used to connect clients to some network. It's also common knowledge that stuff in ones house is not to be taken even if left unlocked. So that point is null, since we can't relate to long established asumptions. Same goes for poking around your telcos wiring that is not a part of your house.
This technology is relatively new. If the services offered by the open wireless cloud are unrestricted, so far it would seem it is okay to use it in a non malicious way. It is the responsibility of the owner of the AP providing the wireless cloud to know what he/she is doing, otherwise not run it. It is also the responsibilty of the wireless hardware providers to sell such hardware preconfigured or upon install mandatorily configured to a secure, non open state. If the owner changes from the deault to an open cloud, then the owner takes all responsibilty over the service he provides. It seems there should also be an addition to the connection protocol to enable a banner message, like ftp and .message or even system wise issue.net. That way one can clearly read if he/she is allowing access to all or it is restricted. -- Robi -- general wireless list, a bawug thing <http://www.bawug.org/> [un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless
