16:03:13 RRSAgent has joined #webappsec 16:03:13 logging to http://www.w3.org/2014/02/26-webappsec-irc 16:03:20 http://lists.w3.org/Archives/Public/public-webappsec/2014Feb/0128.html 16:03:33 Meeting: WebAppSec WG Teleconference 26-Feb-2014 16:03:37 Chairs: bhill2, ekr 16:03:40 Agenda: http://lists.w3.org/Archives/Public/public-webappsec/2014Feb/0128.html 16:03:53 zakim, who is here? 16:03:53 sorry, bhill2, I don't know what conference this is 16:03:54 On IRC I see RRSAgent, Zakim, bhill2, terri, gmaone, PeteF, glenn, anssik, timeless, mkwst, tobie__, wseltzer, trackbot 16:03:58 zakim, this is 92794 16:03:58 ok, bhill2; that matches SEC_WASWG()11:00AM 16:04:00 +??P22 16:04:03 zakim, who is here? 16:04:03 On the phone I see +49.162.102.aaaa, terri, BHill, +1.315.849.aabb, [Mozilla], [GVoice], ??P22 16:04:06 On IRC I see RRSAgent, Zakim, bhill2, terri, gmaone, PeteF, glenn, anssik, timeless, mkwst, tobie__, wseltzer, trackbot 16:04:11 zakim, who is talking? 16:04:18 Zakim, ??P22 is gmaone 16:04:18 +gmaone; got it 16:04:22 ekr has joined #webappsec 16:04:23 mkwst, listening for 10 seconds I heard sound from the following: BHill (39%) 16:04:40 zakim, [Mozilla] has grobinson 16:04:40 +grobinson; got it 16:04:49 +glenn 16:05:06 wuwei_ has joined #webappsec 16:05:15 zakim, aaaa is mkwst. 16:05:16 +mkwst; got it 16:05:52 +1.315.849.aabb is Pete Freitag... just listening in 16:06:15 zakim, who is here? 16:06:15 On the phone I see mkwst, terri, BHill, +1.315.849.aabb, [Mozilla], [GVoice], gmaone, glenn 16:06:17 [Mozilla] has grobinson 16:06:17 On IRC I see wuwei_, ekr, RRSAgent, Zakim, bhill2, terri, gmaone, PeteF, glenn, anssik, timeless, mkwst, tobie__, wseltzer, trackbot 16:06:22 grobinson has joined #webappsec 16:06:49 [Mozilla] has ekr 16:06:56 zakim, [mozilla] has ekr 16:06:56 +ekr; got it 16:06:58 zakim, +1.315.849.aabb is PeteF 16:06:58 +PeteF; got it 16:07:51 Scribe: Mike West 16:07:58 Scribenick: mkwst 16:08:09 TOPIC: Minutes approval 16:08:15 http://www.w3.org/2014/02/12-webappsec-minutes.html 16:08:17 + +1.831.246.aacc 16:08:22 bhill: Objections to last time's minutes? 16:08:32 bhill: Approved! 16:08:40 zakim, aacc is dveditz 16:08:40 +dveditz; got it 16:08:48 TOPIC: Agenda Bashing 16:09:18 bhill: How do we get subint to FPWD? 16:09:40 dveditz: Is redirection part of the leakage discussion? 16:09:44 mkwst: yes. 16:09:54 TOPIC: Open Actions Reveiw 16:10:00 https://www.w3.org/2011/webappsec/track/actions/open?sort=owner 16:11:07 bhill: Blobs, dveditz? 16:11:23 mkwst: Current language is that blobs need to be whitelisted explicitly as 'blob:'. 16:11:30 dveditz: Should be ok. 16:11:38 +??P18 16:11:45 dveditz: One thing. 16:12:13 dveditz: 'data:' should not match '*'. 16:12:32 dveditz: 'blob:' too. They should be treated as 'unsafe-inline'. 16:12:53 freddyb_ has joined #webappsec 16:13:13 mkwst: Propose some text? 16:13:21 dveditz: Sure, where? 16:13:33 mkwst: In the matching algorithm section. Could add a note anywhere thought. 16:13:42 dveditz: Intent is to include blob and data. 16:14:17 mkwst: will find some language for you. 16:14:44 TOPIC: Call for consensus on UI Security LCWD 16:14:45 http://lists.w3.org/Archives/Public/public-webappsec/2014Feb/0092.html 16:15:07 bhill: CfC for UI Security to LCWD last week. 16:15:14 bhill: Moved frame-options out into mainline CSP 1.1 16:15:31 bhill: Push previous spec with that bit removed. 16:15:37 bhill: No objections to CfC. 16:16:10 bhill: Motion to move UI Security to LCWD? 16:16:32 ekr: So moved. 16:16:38 second 16:16:46 gmaone: seconded. 16:17:06 bhill: Objection to unanimous consent? 16:17:17 bhill: None heard. LCWD! 16:17:32 RESOLVED: UI Security to be advanced to Last Call Working Draft 16:17:51 TOPIC: Paths, Redirects and information leakage in CSP 16:17:52 http://lists.w3.org/Archives/Public/public-webappsec/2014Feb/0127.html 16:18:38 bhill: Proposals from Mike, Michal, etc. 16:18:44 bhill: summarize? 16:19:09 dveditz: Summary is that we're screwed. Need to either lose functionality, or live with a bad feature. 16:21:18 zakim, who's noisy? 16:21:28 option 1: (Egor's proposal) only enforce policy on initial fetch, not on subsequent redirects 16:21:30 glenn, listening for 11 seconds I heard sound from the following: mkwst (41%) 16:22:13 mkwst: Summary. 16:23:04 mkwst: Two options: 1. Allow redirects for source expressions with paths. This would avoid the biggest problem (reading paths cross-origin via brute force). 16:23:14 option 1 engenders some concern due to widespread presence of open redirectors on many domains 16:24:06 mkwst: 2. drop reporting, drop the DOM event, pretend that a resource failed to load just as if a network error occurred. 16:24:19 option 1 also doesn't really solve the problem, it just rate-limits or makes the attacker use tactics like using a frame-per path tested 16:25:11 dveditz: Reporting isn't the problem. Can tell from the page whether or not the resource loaded. 16:27:24 mkwst: 'script-src example.com/js'. would allow example.com/js/redirect -> evil.com 16:27:33 option 3: fallback to checking only at domain granularity on redirects 16:27:35 dveditz: why wouldn't we fall back to domain level granularity? 16:28:30 mkwst: Complexity. Seems reasonable to have distinct behavior for paths/no-paths. 16:31:18 bhill: Option #1 probably isn't so bad. 16:31:26 bhill: Part of the trust decision for an origin. 16:31:38 bhill: less likely that there's redirects past a whitelisted path 16:31:41 I think that option 1 is the best... 16:31:43 bhill: not that complicated. 16:31:59 simple to implement, explain, trust decision is obvious (including implication of possibility of redirects) 16:32:03 dveditz: Require paths to be a full match for a path segment? 16:32:24 and trust / risk of including a redirector can be reduced by specifying a path instead of a full host 16:34:12 dveditz: Suggested that we not report redirects, report more information about the URL in the document. 16:34:23 dveditz: Want to drop that suggestion. 16:35:48 dveditz: Shouldn't report URL for same-origin redirects. 16:36:50 dveditz: No. I'm saying dont' change the stripping aspect of the spec. 16:38:09 dveditz: One more question: has the reporting turned out to be useful for real-world use cases? 16:38:23 dveditz: Twitter? 16:38:57 q+ 16:39:23 bhill: Folks I've talked to find reporting useful. 16:39:48 bhill: Report-only is useful. Anomaly detection, etc. 16:40:03 bhill: Thought-leader with regard to reporting in the security space. 16:40:24 TOPIC: Extension note text in CSP 16:40:27 dveditz: Reporting isn't always awesome. 16:40:42 ekr: Might not be a Mozilla consensus. 16:41:03 ack glenn 16:41:08 glenn: Worked with a spec that's making reporting optional, except when report-only is used. Might be reasonable to look at. 16:41:34 glenn: Not yet public. 16:41:49 bhill: Reporting does have users. Would make folks unhappy to lose it. 16:42:00 looks like approaching something like: 16:42:14 bhill: Extension note discussion. 16:42:26 glenn: New information, reopening for discussion? 16:42:48 bhill: Groundswell of interest. Folks expressing concern at the resolution of the objection. 16:42:59 "User agents may allow users to modify or bypass CSP enforcement, through user preferences and/or third-party additions to the user-agent" so that we're not tied to specifically bookmarklets and extensions." 16:43:16 gopal has joined #webappsec 16:43:22 or rather "User agents may allow users to modify or bypass CSP enforcement, through user preferences and/or third-party additions to the user-agent." 16:43:38 glenn: Trying to be accommodating of new suggestions. Last suggestions seems close to something we could accept. 16:43:56 dveditz: Normative or non-normative. 16:44:15 What about "User agents should not prevent users from modifying or bypass etc..."? 16:44:18 dveditz: Suggestions for UA should not be normative. 16:44:22 q+ 16:44:22 (or Should? :) ) 16:44:38 grobinson: Third-party additions? 16:44:59 grobinson: Don't want to tacitly accept malware. 16:45:07 grobinson: "User-instigated third-party additions"? 16:45:18 bhill: Wide leeway, non-normative. 16:45:29 bhill: Chrome doesn't allow side-loaded extensions, for example. 16:45:49 bhill: Don't want to ask for special treatment in that sideloading sense. 16:46:36 bhill: Can the editors add that language to the spec? Seems satisfactory to everyone in the community who has expressed interest and concern. 16:46:41 glenn: Ok with this. 16:46:54 glenn: Neglected to remove a related piece of language in 3.2.5.17. 16:47:02 glenn: "ignore this step" bookmarklets. 16:47:07 glenn: Should be remove as well. 16:48:01 glenn: Falls into the category of "user preferences" or "third-party additions". 16:48:25 glenn: But tied to the earlier language. Haven't looked at the editing history, but seem closely related. 16:48:31 glenn: Suggesting that this one should be removed as well. 16:48:38 "User agents may allow users to modify or bypass CSP enforcement, through user preferences, bookmarklets, and/or third-party additions to the user-agent" 16:48:39 glenn: New language covers both. 16:49:05 mkwst: fine with that. 16:51:22 ekr: I don't care. SHOULD vs MAY vs SHOULD NOT. Not useful. 16:51:29 bhill: This text seems reasonable. Let's do it. 16:51:41 bhill: Reflects the consensus. May choose to do this, but not required to. 16:52:04 bhill: Not going to satisfy everyone, but we can live with it. Should close it and move on. 16:52:13 wseltzer: Won't be surprised if we see more argument next week. 16:52:21 that was me, actually 16:52:26 bhill: Not everyone's ever going to be happy about anything. 16:52:41 (not wseltzer, who I haven't heard today) 16:52:45 (Sorry, Terri! Bad with voices...) 16:52:57 ACTION: mkwst to remove 3.2.5.17 16:52:57 bhill: Should remove the 3.2.5.17 text as well. 16:52:57 Error finding 'mkwst'. You can review and register nicknames at . 16:53:15 (bhill: I'm mwest2) 16:53:26 glenn: Should we update CSP 1.0 as well? 16:53:39 glenn: We can edit CR before PR, yes? 16:54:14 bhill: New topic. We have so far declared that we've got consensus on CSP 1.0, moved on. If we want to reopen that, take a poll on the list. 16:54:29 bhill: Discussion has been in regards to 1.1. Let's bring it up on the list. 16:54:55 glenn: Fine with that. Just want to point out, Cox will comment at the PR timeframe. 16:55:12 bhill: Lightning round! 16:55:43 bhill: Outstanding issues with regard to , terri? 16:55:57 terri: If the answer is "nobody knows", that's an answer. We can discuss later. 16:56:22 dveditz: We had policy-uri. Folks outside Mozilla hated it because of latency, and it was in an HTTP header anyway. 16:56:45 terri: Brainstormed other ideas? 16:56:59 terri: Link to discussion? 16:57:10 dveditz: Before the WG. 16:57:19 grobinson: policy-uri being removed from Firefox. Latency. 16:57:35 bhill: search the list (sorry there's no pointer). There was discussion when opening 1.1. 16:57:48 bhill: Application use cases were described. 16:58:48 terri: I think I was around for that. 16:58:54 bhill: Next call in two weeks! 16:59:08 bhill: IETF meeting! Exciting! Security and privacy next week in London! 16:59:13 minor note about process: is it possible to send the notes (or a link to them) to the public-webappsec list? 16:59:15 bhill: Participate remotely! 16:59:26 -glenn 16:59:27 -dveditz 16:59:32 fwiw, I found them hard to google :-) maybe it's just me though 16:59:35 -[Mozilla] 16:59:35 zakim, list attendees 16:59:36 As of this point the attendees have been +49.162.102.aaaa, terri, BHill, [GVoice], gmaone, grobinson, glenn, mkwst, ekr, PeteF, +1.831.246.aacc, dveditz 16:59:41 but it would make the outcome of the call more transparent too 16:59:42 rrsagent, make minutes 16:59:42 I have made the request to generate http://www.w3.org/2014/02/26-webappsec-minutes.html bhill2 16:59:46 thanks bhill2 16:59:47 -gmaone 16:59:49 rrsagent, set logs public-visisible 16:59:59 -??P18 17:00:02 rrsagent, set logs public-visible 17:00:05 -[GVoice] 17:00:06 -mkwst 17:00:14 -PeteF 17:00:17 -BHill 17:00:24 -terri 17:00:25 SEC_WASWG()11:00AM has ended 17:00:25 Attendees were +49.162.102.aaaa, terri, BHill, [GVoice], gmaone, grobinson, glenn, mkwst, ekr, PeteF, +1.831.246.aacc, dveditz 17:40:56 ekr has joined #webappsec 18:19:36 terri has joined #webappsec 18:22:15 ekr has joined #webappsec 18:27:50 gmaone has joined #webappsec 18:32:22 glenn has joined #webappsec 19:04:25 ekr has joined #webappsec 19:27:36 Zakim has left #webappsec 19:32:48 ekr has joined #webappsec 20:12:06 ekr has joined #webappsec 20:33:38 glenn has joined #webappsec 20:54:40 glenn has joined #webappsec