info on the github breach appears to only be available on xitter 🙄 , I fished it out for you.
info on the github breach appears to only be available on xitter 🙄 , I fished it out for you.
@Nephrite you just have to be aware that things you download from the internet can be bad. It's always been that way.
And avoiding anything that has to do with JavaScript helps.
@radex sandboxing the web browser was reasonably easy at the start because web pages had extremely limited functionality. But every time that allowable functionality gets extended, there is another multi-year process of defining and standardizing new interfaces including new permissions.
You cannot do that in an IDE without severely compromising the usefulness of thr IDE's plugin model
@ratsnakegames @Nephrite @0xabad1dea Sure. I'd rather say that _not every_ extension can be meaningfully sandboxed.
Required permissions could be clearly displayed and those that require full unsandboxed access could be additionally flagged.
IMO this would go a long way towards reducing risk of pwnage via extensions. Long process, sure, but worth it.