3 ms·
This paired with the recent web workers exploit [1] shows the direction malicious and pwned sites are very quickly moving. I think a good solution would be to i
by Etheryte 8y ago
This paired with the recent web workers exploit [1] shows the direction malicious and pwned sites are very quickly moving. I think a good solution would be to implement resource control on domain level in browsers and give the user the ability to set the preferred values.
[1] https://www.zdnet.com/article/new-browser-attack-lets-hackers-run-bad-code-even-after-users-leave-a-web-page/ https://www.zdnet.com/article/new-browser-attack-lets-hacker...
- untog 8y agoThat worker exploit doesn't make any sense, as written: > Technically, Service Workers are an update to an older API called Web Workers. However, unlike web workers, a service worker, once registered and activated, can live and run in the page's background, without requiring the user to continue browsing through the site that loaded the service worker. This isn't true. A service worker will be automatically shut down when it isn't attached to a browsing context. Not immediately, but it definitely doesn't support what the article describes.
- Etheryte 8y agoThis is covered in the article. > The attack routine consists of registering a service worker [...] and then abusing the Service Worker SyncManager interface to keep the service worker alive after the user navigates away.