Re: Delegation is the Cornerstone of Civilization: Sharing in Sandstorm.io

I’m not clear on how that works, as router variation (in fact all small area network configuration variation) is one of the nasties of IoT.  Is the users’ table concept something from Cap’n Proto, or Sandstorm?  

I think that a barrier for many situations would be working with ISPs to wrest the control from their routers for access to in-premises Things.

The concept of user management to control access is one thing that I’m trying to avoid through the use of capabilities as I believe that access to Things will needs to be shared, even if the Things are s/w entities running on devices which current models regard as ‘owned’ (eg mobile phones).

The flip side is making it obvious to users who they’ve handed off some trust to in the past (which neighbour borrowed my ladder and ‘forgot’ to bring it back).

Tim
> On 7 May 2015, at 21:57, David Nicol <[email protected]> wrote:
> 
> On Thu, May 7, 2015 at 3:07 PM, Kenton Varda <[email protected]> wrote:
>> IoT desperately needs a way to manage devices that doesn't involve ceding
>> all control to centralized SaaS services.
> 
> Proposed first step: compose and implement a wide and flat API for a
> Linux network appliance, such as a DD-WRT installation, separating all
> possible router configuration operations into explicit categories,
> thereby making it possible to, for instance, provide a capability key
> string which allows the bearer to set firewall rules pertaining to one
> internal IP address only, without bothering with a users table at all,
> and so on.
> 
> 
> 
> -- 
> 8mm shafts with 5/16" 24 TPI threads
> _______________________________________________
> cap-talk mailing list
> [email protected]
> http://www.eros-os.org/mailman/listinfo/cap-talk

_______________________________________________
cap-talk mailing list
[email protected]
http://www.eros-os.org/mailman/listinfo/cap-talk