Re: Capability allegories
"Mark S. Miller" <[email protected]> Tue, 2 Feb 2016 13:23:00 -0800
| Newsgroups | gmane.comp.capabilities.general |
|---|---|
| Message-ID | <CABHxS9h=oSG48D7P+4LEqOPV_-_3OFjou8BF7a3B_mSKFbgpsA@mail.gmail.com> |
--===============6715059862979583107== Content-Type: multipart/alternative; boundary=001a11422b2022aa0c052ad01b52 --001a11422b2022aa0c052ad01b52 Content-Type: text/plain; charset=UTF-8 Unless I am missing something, I don't see how Eve is the story is a Confused Deputy, in the security sense of the term as coined and explained in Norm's paper <http://www.cis.upenn.edu/~KeyKOS/ConfusedDeputy.html>. The "Confused Deputy" is about a threat much more specific than the general threat of confusing a deputy. See Tyler Close's "ACLs don't" < http://waterken.sourceforge.net/aclsdont/current.pdf> for IMO the clearest explanation of how to think about the Confused Deputy, and what is and is not a Confused Deputy problem. (My own Capability Myths Demolished < http://srl.cs.jhu.edu/pubs/SRL2003-02.pdf> is also good and complementary.) On Tue, Feb 2, 2016 at 10:00 AM, Matt Rice <[email protected]> wrote: > Rob has shared the Rumpelstiltskin interpretation, > > One of the examples i have used to explain the confused deputy, > is in Genesis (from the bible) > > Eve in the story is both described as both helper, and tricked > it has the benefit of being both well known, and the word of god. > _______________________________________________ > cap-talk mailing list > [email protected] > http://www.eros-os.org/mailman/listinfo/cap-talk > -- Cheers, --MarkM --001a11422b2022aa0c052ad01b52 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div><div>Unless I am missing something, I don't see h= ow Eve is the story is a Confused Deputy, in the security sense of the term= as coined and explained in Norm's paper <<a href=3D"http://www.cis.= upenn.edu/~KeyKOS/ConfusedDeputy.html">http://www.cis.upenn.edu/~KeyKOS/Con= fusedDeputy.html</a>>.</div></div><div><br></div>The "Confused Depu= ty" is about a threat much more specific than the general threat of co= nfusing a deputy. See Tyler Close's "ACLs don't" <<a h= ref=3D"http://waterken.sourceforge.net/aclsdont/current.pdf">http://waterke= n.sourceforge.net/aclsdont/current.pdf</a>> for IMO the clearest explana= tion of how to think about the Confused Deputy, and what is and is not a Co= nfused Deputy problem. (My own Capability Myths Demolished <<a href=3D"h= ttp://srl.cs.jhu.edu/pubs/SRL2003-02.pdf">http://srl.cs.jhu.edu/pubs/SRL200= 3-02.pdf</a>> is also good and complementary.)<div><br></div><div><br></= div><div><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail= _quote">On Tue, Feb 2, 2016 at 10:00 AM, Matt Rice <span dir=3D"ltr"><<a= href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>&= gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 = 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Rob has shared the Rump= elstiltskin interpretation,<br> <br> One of the examples i have used to explain the confused deputy,<br> is in Genesis (from the bible)<br> <br> Eve in the story is both described as both helper, and tricked<br> it has the benefit of being both well known, and the word of god.<br> _______________________________________________<br> cap-talk mailing list<br> <a href=3D"mailto:[email protected]">[email protected]</a><= br> <a href=3D"http://www.eros-os.org/mailman/listinfo/cap-talk" rel=3D"norefer= rer" target=3D"_blank">http://www.eros-os.org/mailman/listinfo/cap-talk</a>= <br> </blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class= =3D"gmail_signature">=C2=A0 =C2=A0 Cheers,<br>=C2=A0 =C2=A0 --MarkM</div> </div> --001a11422b2022aa0c052ad01b52-- --===============6715059862979583107== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ cap-talk mailing list [email protected] http://www.eros-os.org/mailman/listinfo/cap-talk --===============6715059862979583107==--