POLA Would Have Prevented the Event-Stream Incident
9 views
Skip to first unread message
Mark Miller
unread,
Dec 3, 2018, 5:36:06 PM12/3/18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Discussion of E and other capability languages, cap-...@googlegroups.com, Google Caja Discuss
The npm / event-stream incident is the perfect teaching moment for POLA (Principle of Least Authority), and for the need to support least authority for JavaScript libraries.
At the recent (November 2018) tc39 meeting, I presented on the enhancements needed to support least authority for JavaScript modules and libraries, adequate to have prevented this incident.
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to e-l...@googlegroups.com, cap-...@googlegroups.com, Google Caja Discuss
A critical vulnerability has just been announced in Kubernetes (https://github.com/kubernetes/kubernetes/issues/71411) that also appears to be a confused deputy. I probably won’t have time myself, but a write-up of this issue would be another good POLA teaching opportunity in my opinion (e.g., use of capabilities/macaroons vs TLS client authentication to convey authority through a complex distributed system).