You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My main reservation about experimenting with such a powerful & clever thing involves potential security concerns.
Every extension is a little worrisome, but in general open-source plus sufficient-community-of-users plus browser-store-review plus browser-security-boundaries will put me at ease.
But, a custom C-language filesystem, and specifically one that gets pushed JSON data derived from any untrusted website, gives extra pause.
Has the FS code been subjected to any/some/much intense review for security risks? Could it be, on either a volunteer or contracted/crowdfunded basis? Its small size & relative low-rate-of-change even as browser-visible features grow suggest a one-time (or very occasional) bounded effort/cost could offer a long period of peace-of-mind.
The text was updated successfully, but these errors were encountered:
My main reservation about experimenting with such a powerful & clever thing involves potential security concerns.
Every extension is a little worrisome, but in general open-source plus sufficient-community-of-users plus browser-store-review plus browser-security-boundaries will put me at ease.
But, a custom C-language filesystem, and specifically one that gets pushed JSON data derived from any untrusted website, gives extra pause.
Has the FS code been subjected to any/some/much intense review for security risks? Could it be, on either a volunteer or contracted/crowdfunded basis? Its small size & relative low-rate-of-change even as browser-visible features grow suggest a one-time (or very occasional) bounded effort/cost could offer a long period of peace-of-mind.
The text was updated successfully, but these errors were encountered: