Hacker News new | past | comments | ask | show | jobs | submit login

> All the problems with security seem to come from JavaScript exploits intrinsic to the engine

Yes the classic memory-related bugs come from the engine, but the comment explicitely mentioned leaks and I don't think that was about the memory ones. Many of the new "features" turned out to leak sensitive or at least identification-enabling information. Imo having remote code execution without a big red warning that this is stupid and you should not do it that users can't click away without being forced to think about it just isn't a good idea, even if it is sandboxed. At the very least we should have a permission-based system where users need to authorize every single Javascript API, for every single connection/file/database/whatever and be unable to ignore it without disabling the APIs. That would imo be the best compromise since web-devs would be forced to think about what they are doing to users computers¹ while still allowing applications to be built.

¹ My hope being that they wouldn't include [bullshit fontend framework] except when absolutely necessary




I think you underestimate the number of users who would either blanket-approve everything or switch to a browser that doesn't nag so much. Most people care very little about their privacy online.


Relevant:

https://twitter.com/JimMcKeeth/status/692596120464150528/pho...

Indeed, users don't read error messages, and will just click whatever they think they need to click to move on.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: