- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Thu, 11 Jun 2009 09:56:12 +1200
On Thu, Jun 11, 2009 at 5:24 AM, Drew Wilson <atwilson at google.com> wrote: > That's a great approach. Is the pool of OS threads per-domain, or per > browser instance (i.e. can a domain DoS the workers of other domains by > firing off several infinite-loop workers)? Seems like having a per-domain > thread pool is an ideal solution to this problem. > You probably still want a global limit, or else malicious sites can DoS your entire OS by spawning workers in many synthetic domains. Making the limit per-eTLD instead of per-domain would help a bit, but maybe not very much. Same goes for other kinds of resources; there's no really perfect solution to DoS attacks against browsers, AFAICT. Rob -- "He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090611/8936bb10/attachment-0001.htm>
Received on Wednesday, 10 June 2009 14:56:12 UTC