[tor-dev] "old style" hidden services after Prop224
razvan.dragomirescu at veri.fi
Mon Sep 12 13:33:18 UTC 2016
I've pretty much completed a proof of concept of my SIM4Things project (an
IP6 overlay for the Internet of Things running on top of Tor with
persistent secure cryptographic identities tied to physical SIM cards).
I've developed against the current hidden service infrastructure and it
appears to work like a charm, but I'm a bit worried about Prop224. That
will break both the OnionBalance-like service re-registration that I'm
using _and_ the OnionCat HS to IP6 mapping. I know that efforts are in
place to upgrade the two in view of Prop224 but I'm wondering if there's
any good reason to drop support for "old style" hidden services once
Prop224 is fully deployed.
What does everyone think? My vote would obviously be to keep it around,
even if it's no longer the default. Do you see any security implications in
doing so? Is there any hard reason to drop the existing model altogether at
some point and if so, what is the plan for transition? My hidden services
would be very low traffic (Internet of Things, sensor measurements, etc)
but hard to upgrade in the field. Also, by design, we have no control over
the endpoints once deployed (only their owner can access them), so we
cannot force an upgrade, we can just suggest it to the owner and come up
with a procedure for them to do so.
Chief Technology Officer
Cayenne Graphics SRL
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the tor-dev