Archived from groups: alt.internet.wireless (
More info?)
Good point, but lots of people accidentally connect to open wifi nets
without even knowing they are doing so. For example, they may be configured
to autoconnect to the strongest signal available. In this case, they never
even see the SSID.
As for PDAs synching email over wifi, can't they be configured to use WEP?
The example proposed not using the splash page if encryption is enabled, and
giving you a way to disable it if you really want to run wide-open and
unsecured.
The whole thing is moot, because I can't imagine courts actually finding
that you did all that could be reasonably expected to prevent your internet
connection from being abused, when everybody with a wifi router has
encryption available, however imperfect it is.
"shope" <stephen_hope@xntlxworld.com> wrote in message
news:sBcmc.221$2A5.110@newsfe1-win...
>
> "gary" <pleasenospam@sbcglobal.net> wrote in message
> news:5%8mc.24405$py7.9486@newssvr22.news.prodigy.com...
> > Even No Trespassing signs are hard to enforce. Enforced towing for
> > restricted parking is another example. In my city, you are required to
> mark
> > restricted spaces clearly, and to post several signs in visible places,
> with
> > certain language that has been enshrined by legal precedent as
> enforceable.
> > If you fail to do all of these things just right, if you have someone
> towed,
> > you may end up paying for it yourself.
>
> Web access seems over complex - what happens if i have a wireless device
> that doesnt understand http, or isnt driven by a user (maybe a background
> email sync process on a PDA?)
>
> if all you need is to show that this isnt a connection intended for
> "unfettered" access, then why not show that within the SSID?
>
> Naming it something like "no_trespassing" or "private" seems pretty
> unambiguous.
> >
> > Relying on a warning means that some rule has to be accepted about how
the
> > warning is worded. This has to be tested in court - if it's too vague,
or
> > doesn't meet some obscure civil code requirement, it's not enforceable.
If
> > you want vendors to put these splash pages in the router, then the
wording
> > has to work in every state, and every state, county, and city will have
> > local laws and ordinances that affect interpretation. But wait - they
> market
> > in Europe, too. Is any of this legal or even meaningful in Europe?
Vendors
> > aren't going to bother to put in this feature unless it actually works,
at
> > least in the U.S. Now, they could put in a feature that allows the user
to
> > configure the page. But now we're talking about increased cost - they
have
> > to design an interface to let you modify the page, allocate flash memory
> to
> > store the modifications, and so on. And, in the end, the splash page now
> has
> > to be configured and selected by the user. The whole original point was
> that
> > it should be a trivial out-of-box thing that works by default unless the
> > user takes steps to disable it.
> >
> > Plus, you always have the much stronger tool of encryption available.
> Given
> > how ineffective a warning is compared to encryption, why would courts
> decide
> > to accept the warning as sufficient due diligence, if a much stronger
> > medicine is available on every 802.11 router manufactured today, and is
> part
> > of the standard?
> >
> >
> > "mhicaoidh" <®êmõvé_mhic_aoidh@hotÑîXmailSPäM.com> wrote in message
> > news:xx8mc.36792$Ik.2317683@attbi_s53...
> > > Taking a moment's reflection, gary mused:
> > > |
> > > | In any case, it's moot. I don't think a splash page helps much
without
> > > | secure authentication.
> > >
> > > Well, it would be the wireless equivalent to a No Trespassing
sign.
> > > They really don't stop anyone, but people still hang them up.
> --
> Regards
>
> Stephen Hope - return address needs fewer xxs
>
>