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

On Fri, May 8, 2015 at 3:58 AM, Tim Coote <[email protected]> wrote:
> 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?

the users' table is traditionally a colon-delimited ASCII file in the
file system at /etc/password. I don't know how DD-WRT (a popular
hobbyist replacement for the vendor-provided embedded OS on common
off-the-shelf routers) works, specifically. A "hardened" DD-WRT would
have obvious appeal and may exist already.

> 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.

Huh? Not proposing any such thing. Proposing fine-grained access to
the first hop in from the wall as a demonstration platform for the
benefits of fine-grained capability-based security and experience
using it.

> 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).

As an embedded linux, DD-WRT probably has user-based access control
but not at a grain fine enough to delegate arbitrary things -- like,
delegate a capability to change the static MAC addresses associated in
DHCP with particular internal IP addresses, without allowing access to
anything else. On the other hand, it might already. I don't know.

I am suggesting/proposing hobbyist replacements for home router
equipment software as a good demonstration platform.


-- 
8mm shafts with 5/16" 24 TPI threads
_______________________________________________
cap-talk mailing list
[email protected]
http://www.eros-os.org/mailman/listinfo/cap-talk