[HamWAN PSDR] Holy smokes, we have Internet address space!

Benjamin Krueger ben.krueger at gmail.com
Fri Feb 22 14:20:02 PST 2013


Lets be super clear here. We're not building a general use ISP. It's an
experimental open network. We'll provide the best integrity controls we
can, but there are no promises and every participant should know exactly
what they're getting in to.


On Fri, Feb 22, 2013 at 2:12 PM, The Doctor <drwho at virtadpt.net> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 02/21/2013 05:05 PM, Benjamin Krueger wrote:
> > We really need to think long and hard about whether it's a good
> > idea to connect this network to the internet. I am still
> > unconvinced of the value of this proposition, and it causes a great
> > many extremely difficult technical and legal challenges.
>
> In the US, unless the account you have with a broadband ISP
> specifically permits connection sharing (especially public connection
> sharing), they may threaten to kill your access unless you take the
> gateway to the mesh network down.  They may also decide to drop you as
> a customer entirely and be done with you.
>
> Additionally, there are several states that have laws against doing
> just this.  Community wireless networks run into this problem a lot
> and not a few have been shut down here.  It was a common complaint
> from USian projects at the last International Summit for Community
> Wireless Networks (this link was referenced a lot during the "State of
> wireless" roundtable discussion:
> http://www.cybertelecom.org/broadband/muni.htm).
>
> > If nothing else, it is a distraction for us today. If we really
> > want to explore that feature of the network, we should do it in a
> > future phase after the network is already established. In the
> > meantime, we can block
>
> That would be a good strategy.  In addition, you will want to have a
> large community of active users to help you make a case for not being
> shut down if it comes to it.
>
> > traditionally encrypted ports on the network as standard practice;
> > no need for one-off changes from end-users.
>
> The problem there is that you will then be forcing users to connect to
> online services insecurely.  Passive attackers will be able to easily
> record authentication credentials to webmail services (which are
> increasingly being used as authentication providers by other services
> - - Google Mail comes to mind immediately), banks, and other sites.
>
> You might be incurring additional liability if you set that policy.
> You might also want to reconsider setting up network gateways for this
> reason.
>
> - --
> The Doctor [412/724/301/703] [ZS]
> Developer, Project Byzantium: http://project-byzantium.org/
>
> PGP: 0x807B17C1 / 7960 1CDC 85C9 0B63 8D9F  DD89 3BD8 FF2B 807B 17C1
> WWW: https://drwho.virtadpt.net/
>
> "I'm prophetic, not infallible." --Mr. Morden
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
> Comment: Using GnuPG with undefined - http://www.enigmail.net/
>
> iEYEARECAAYFAlEn7T0ACgkQO9j/K4B7F8GNJQCeJSnodhgNVAo0OG+UUs4Dhj4z
> Q6EAoKoHM9VH2aPdOkFW6LWPIl35y1Zt
> =R4B0
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> PSDR mailing list
> PSDR at hamwan.org
> http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
>



-- 
Benjamin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.hamwan.net/pipermail/psdr/attachments/20130222/5563ecfc/attachment.html>


More information about the PSDR mailing list