[Freedombox-discuss] Hosting public services (was: Re: Bootstrapping a Freedombox contact list)

Anders Jackson anders.jackson at gmail.com
Tue Nov 26 10:00:23 UTC 2013

Den 26 nov 2013 09:19 skrev "Tim Retout" <diocles at debian.org>:
> On Wed, 2013-11-20 at 23:57 +0100, Petter Reinholdtsen wrote:
> > [Tim Retout]
> > > Future extensions:
> > > ==================
> > [...]
> > > - How would services on public IPs be offered? (UPnP to punch
> > > through the router, and then Freedombuddy tells others about them?)
> >
> > I suspect something like pagekite is the way forward here, at least as
> > an option if uPnP or similar isn't an option.  At least with my ISP,
> > port 80 is blocked on inbound traffic. :(
> I agree Pagekite is nice because it sidesteps dynamic home IPs by
> proxying back from a public server, and it gives you a name in the
> "real" DNS system.  You can use CNAMEs to point your own domain name at
> the pagekite.me names, or potentially run your own Pagekite server
> instance.

If using a tunnel is OK, why not use IPv6 directly, maybe with SecureIP?

> This implies that hiding a given Freedombox's IP from Pagekite/the NSA
> is not a requirement. :)
> Part of me worries that this is a sort-of-centralized solution.  I think
> this is okay from a security point of view - we just treat the server as
> an untrusted part of the network link.  Have you tried running your own
> pagekite server?
> The other limitation is that only HTTP, HTTPS and SSH are handled by
> Pagekite.  I would quite like to support mail protocols and XMPP too.

Well, IPv6 is supported by IPv6.
> --
> Tim Retout <diocles at debian.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/freedombox-discuss/attachments/20131126/d6f8a24d/attachment.html>

More information about the Freedombox-discuss mailing list