Re: Security review of Resource Timing
Steve Workman <[email protected]> Wed, 27 Apr 2016 11:25:28 -0700
| Newsgroups | gmane.comp.mozilla.security |
|---|---|
| Message-ID | <CACARDexqSKBvTqAfuRBgB1soUutqc6fY++Ljy_-zz8xqxi7muw@mail.gmail.com> |
Tanvi, Dan or Richard might have some input here. On Wed, Apr 27, 2016 at 1:23 AM, Anne van Kesteren <[email protected]> wrote: > Hey, in https://github.com/w3c/resource-timing/issues/12 folks are > looking for Mozilla to give some kind of security sign off. It's still > not entirely clear to me how we do this kind of thing as an > organization so I thought I'd ask here. > > In particular, I know in the past we've been conservative revealing > the specifics of network failures, even when it comes to same-origin > communication. The outcome is that a ton of APIs expose that kind of > thing binary, either it works or it didn't. > > Now https://w3c.github.io/resource-timing/ promises to give detailed > information, even cross-origin if the resource on the other side opted > in, for DNS, TLS, HTTP, etc. timing, even when the resource could not > be completely obtained (the timings for the bits where it started > failing will be zero). > > It's not entirely clear to me if this enables new attacks, and of what > nature, but it does seem like a significant shift in policy from the > tried and true binary approach. > > Input appreciated. > > > -- > https://annevankesteren.nl/ > _______________________________________________ > dev-security mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-security >