Re:The Signal protocol for Node and browsers
by bugmen0t on Thursday December 15, 2016 @08:43AM
(#13184489)
Two notes:
2) There is interest and progress on securing web applications: - For early research papers look into 'Privilege Separation in HTML5 Applications' by Devdatta Akhawe et al. <https://www.usenix.org/system/files/conference/usenixsecurit.... - For more practical concerns, see the stuff coming out of the W3C WebAppSec Working Group (CSP, Suborigins, etc.). - For Sandboxing/Compartmentalization of code, see the Realms proposal coming in to a future version of ECMAScript (JavaScript): <https://github.com/caridy/proposal-realms>
2) Firefox new-style extensions (WebExtensions) are in fact least-privilege.
Further adding to it are untethered, unchecked extensions in eg. Firefox. Every extension in Firefox is essentially running with full "browser root" privileges. Chrome at least has a privilege system that tries to avoid allowing every extension to attach a debugger to anything.
(I was also surprised that "how do i run that untrusted JS in my JS context 'safely'?" is a question asked and answered many times)