3 ms·
Change of ownership is easily gamed though. The change can be hidden or the extension can be "leased for 99 years" or whatever. It really makes me wonder if th
by crazygringo 3y ago
Change of ownership is easily gamed though. The change can be hidden or the extension can be "leased for 99 years" or whatever.
It really makes me wonder if there's a way to formalize a system of verification, trust, vouching, etc. not just for extensions but for source-viewable software in general, version by version, diff by diff.
Volunteers actually inspect an extension's JavaScript to check for anything potentially malicious (is it reporting on user activity etc.), they vouch for each other, and you select some core single individual or group to trust (or majority-vote or something), and then only allow software on your system that is vouched for. Nothing ever gets upgraded until it passes.
- woodruffw 3y agoThese types of problems roughly map onto the distributed identity problem: there's no known way to distribute `K` authority identities to `M` trusting identities without some kind of trusted intermediate. "Vouching" can form that kind of trusted intermediate, but probably not without grinding an ordinary speedy update process to a near halt. That's probably a worse outcome than just having the pre-existing authority (i.e., Mozilla or Google) establish an enforceable policy around what constitutes an acceptable (or acceptably transparent) update.