21:00:47 RRSAgent has joined #webappsec 21:00:47 logging to http://www.w3.org/2012/09/25-webappsec-irc 21:00:49 RRSAgent, make logs world 21:00:49 Zakim has joined #webappsec 21:00:51 Zakim, this will be 21:00:51 I don't understand 'this will be', trackbot 21:00:52 Meeting: Web Application Security Working Group Teleconference 21:00:52 Date: 25 September 2012 21:01:02 fred has joined #webappsec 21:01:05 scribe: tanvi 21:01:14 trackbot-ng, start telcon 21:01:15 jeffh has joined #webappsec 21:01:16 RRSAgent, make logs world 21:01:18 Zakim, this will be 21:01:18 I don't understand 'this will be', trackbot 21:01:19 Meeting: Web Application Security Working Group Teleconference 21:01:19 Date: 25 September 2012 21:01:28 Zakim, this will be Meeting: Web Application Security Working Group Teleconference 21:01:28 I do not see a conference matching that name scheduled within the next hour, tanvi 21:01:28 2:01 21:01:28 Date: 25 September 2012 21:02:05 zakim, who is here? 21:02:05 sorry, ekr, I don't know what conference this is 21:02:06 On IRC I see jeffh, fred, Zakim, RRSAgent, ekr, tanvi, gioma1, gopal, erlend, caribou, bhill2, odinho, tobie, timeless, mkwst, Velmont, trackbot 21:02:35 ccarson has joined #webappsec 21:03:04 meeting: Web Application Security Working Group Teleconference 21:03:21 scribenick: tanvi 21:03:23 meeting: Web Application Security Working Group Teleconference 21:03:35 zakim, who is here 21:03:35 tanvi, you need to end that query with '?' 21:03:42 zakim, who is here? 21:03:42 sorry, tanvi, I don't know what conference this is 21:03:43 On IRC I see ccarson, jeffh, fred, Zakim, RRSAgent, ekr, tanvi, gioma1, gopal, erlend, caribou, bhill2, odinho, tobie, timeless, mkwst, Velmont, trackbot 21:04:02 rrsgent, make logs 21:04:06 rrsagent, make logs 21:04:06 I'm logging. I don't understand 'make logs', ekr. Try /msg RRSAgent help 21:04:19 rrsagent, draft minutes 21:04:19 I have made the request to generate http://www.w3.org/2012/09/25-webappsec-minutes.html ekr 21:05:02 jeffh on phone 21:05:09 erlend is on the phone 21:05:56 zakim, who is here? 21:05:56 On the phone I see ??P0, [Mozilla], ccarson, ekr, ??P1, jeffh, +1.978.944.aaaa, ??P7 21:05:58 On IRC I see ccarson, jeffh, fred, Zakim, RRSAgent, ekr, tanvi, gioma1, gopal, erlend, caribou, bhill2, odinho, tobie, timeless, mkwst, Velmont, trackbot 21:06:17 -??P7 21:06:25 Zakim, [Mozilla] is tanvi 21:06:25 +tanvi; got it 21:06:34 fred, tobie, timeless, and velmont not actually here 21:06:35 +??P7 21:06:50 +??P8 21:06:52 Zakim, ??P0 is mkwst 21:06:52 +mkwst; got it 21:06:53 Zakim, ??P7 is gioma1 21:06:54 +gioma1; got it 21:07:13 http://www.w3.org/2012/09/11-webappsec-minutes.html 21:07:36 ekr: approval from last weeks meeting notes 21:07:36 Zakim, ??P1 is erlend 21:07:36 +erlend; got it 21:07:41 ekr: http://www.w3.org/2012/09/11-webappsec-minutes.html 21:07:51 dveditz has joined #webappsec 21:08:04 ekr: agenda bashing? no issues 21:08:15 http://www.w3.org/2011/webappsec/minutes/WebAppSec-minutes-11-Sep-2012.html 21:08:20 edited minutes there 21:08:21 ekr: open issues. http://www.w3.org/2011/webappsec/track/issues/open 21:08:31 ekr: no open issues. 21:08:51 http://www.w3.org/2011/webappsec/track/actions/open 21:08:59 ekr: open actions - http://www.w3.org/2011/webappsec/track/actions/open 21:09:09 http://www.w3.org/2011/webappsec/track/actions/76 21:09:13 ekr: most action items assigned to people who are not here today 21:09:22 ekr: ACTION-76 assigned to gopal 21:09:51 ekr: quite a few tests running. will go back and check 21:09:57 sorry... 21:10:03 gopal: quite a few tests running.  will go back and check 21:10:11 ekr: should we push out a couple weeks? 21:10:51 gopal: yeah. we are checking test coverage. we have a bunch of tests running, but dont' have an idea on what specific features are at risk. 21:11:49 ekr: issues on the mailing list to go over 21:12:05 ekr: long thread about whether there is a privacy threat due to mandatory csp enforcement 21:12:24 mike: the one point i was clear of, was the concept of extensions in browsers potentially visibile to a website thats using csp 21:13:04 mike: if a resource from an extension violates the pages' policy. then server get a report saying that that resource violated csp 21:13:27 mike: and can determine what extension the user is running 21:13:44 dveditz: the extension part is real. working with twitter, there were more violations than should be, and some from addons 21:14:02 dveditz: nothing in the spec that would prevent the user agent from allowing addons to make an exception for themselves 21:14:15 ??: spec says that extensiosn and addons shoudn't be affected by csp 21:14:25 dveditz: in right now firefox there are, but we consider that a bug 21:14:33 ??: in webkit and chrome they are as well and we also consider that a bug 21:15:14 can it be avoided 21:15:19 dveditz: User agent. maybe i changed my user agent to xx to hide myself, but the csp errors show that i am actually firefox. coudl be a problem for the tor bundle (though right now it only uses firefox) 21:15:40 dveditz: so could turn of csp completely. but not the safest thing to do 21:15:58 ??: creating a user agent in such a way that it enhances user privacy 21:16:08 (can ?? identify themselves) 21:16:55 ??: spec is clear that extensions shouldn't affect csp. the spec is quite clear on this point. there is some discussion that user agents are having about how to do this. 21:17:00 ?? is apparently referring to the new W3C "Privacy Interest Group" 21:17:13 zakim, who is making noise? 21:17:26 /cgi-bin/blockpage.cgi?ws-session 21:17:27 dveditz: do noting to the spec, but firefox and webkit have bugs 21:17:30 zakim, who is talking? 21:17:30 http://www.w3.org/community/groups/proposed/#pua 21:17:31 fred is Fredrick Andrews 21:17:32 ekr, listening for 10 seconds I heard sound from the following: erlend (42%) 21:17:47 tanvi: ?? is me. :) 21:17:47 ekr, listening for 12 seconds I heard sound from the following: erlend (23%), ??P8 (79%) 21:17:53 mike west. 21:17:53 dveditz: twitter encountered a lot more modified content 21:17:57 thanks mike 21:18:04 s/??/mkwst/ 21:18:10 whoever is ??P8 should tell zakim. 21:18:49 zakim, who is here 21:18:49 dveditz, you need to end that query with '?' 21:18:51 mkwst: if dealing with active network attacker, csp not helpful. which is why we request people use https 21:18:59 zakim, who is here? 21:18:59 On the phone I see mkwst, tanvi, ccarson, ekr, erlend, jeffh, +1.978.944.aaaa, gioma1, ??P8 21:19:01 On IRC I see dveditz, ccarson, jeffh, fred, Zakim, RRSAgent, ekr, tanvi, gioma1, erlend, caribou, bhill2, odinho, tobie, timeless, mkwst, Velmont, trackbot 21:19:03 ekr: unsafe inline for style source 21:19:58 tanvi: what does unsafe-inline really mean for style-src? 21:20:53 dveditz: in principal we all agree, but some edge cases we have to work out 21:21:15 dveditz: the only one i dont entirely agree about is that you could argue that adding css text property is invoking the parser and therefore might coutn as inline styles 21:21:57 dveditz: otherwise agree with all the other DOM manipulations of inline style is not covered by inline style. directive intended to protect against injected content. 21:22:12 mkswt: write another email that says that 21:22:33 dveditz: implementation wise, it may be easier to drop this. 21:23:01 dveditz: still unclear, even after mail thread, about why we care so much about inline style 21:23:46 dveditz: the old browser that included executable like things. all the browser have dropped that dangerous stuff. 21:24:13 dveditz: although adam's comments about new css features are valid 21:24:28 ekr: dveditz still think about this some and then raise again if an issue 21:24:34 ekr: moving on to next item... 21:24:45 tanvi: interaction of csp sandbox and meta tag 21:25:04 dveditz: 1.1 issue 21:25:41 tanvi: confused on the conclusion from the thread 21:25:52 ekr: bring it up on the next call when adam and jacob are here 21:25:55 - +1.978.944.aaaa 21:26:11 ekr: csp connect-src and browser plugins raised by erlend 21:26:34 erlend: thinking in terms of things like flash, can make http requests that include the cookies the user has at the time 21:26:45 erlend: that is what brought up the subject 21:26:51 dveditz: i think the spec probably shoudl be clearer 21:27:21 dveditz: i know what we did in firefox, but after the issue was raised i realized we were sort of guessing. it's easy to promise more thatn the browser can deliver since plugins can mkae their own network requests independent of the browser 21:27:35 dveditz: some web author may think they are sandboxing more than they are 21:27:59 ekr: but then they wouldnt have access to cookies. ?? 21:28:23 dveditz: sometimes they are just reading data. but often in playlist situation (ex: youtube), loading a whole new chunk of plugin content 21:29:07 ekr: final agenda item is on web crypto wg 21:29:18 ekr: webcrypto wg announced FPWD 21:29:39 http://www.w3.org/TR/WebCryptoAPI/ 21:29:59 -jeffh 21:30:06 -ccarson 21:30:10 -ekr 21:30:14 -gioma1 21:30:18 -mkwst 21:30:19 -erlend 21:30:22 http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet 21:30:28 rrsagent, generate minutes 21:30:28 I have made the request to generate http://www.w3.org/2012/09/25-webappsec-minutes.html tanvi 21:30:38 thx all, l8r 21:30:42 -??P8 21:30:49 -tanvi 21:30:50 ah… I was ??P8 21:30:51 SEC_WASWG()5:00PM has ended 21:30:51 Attendees were ccarson, ekr, jeffh, +1.978.944.aaaa, tanvi, mkwst, gioma1, erlend 21:30:51 rrsagent, stop log 21:30:51 I'm logging. I don't understand 'stop log', tanvi. Try /msg RRSAgent help 21:31:02 sorry, I was half-wayt o hanging up 21:31:59 no problem, hopefully that worked 21:32:11 that looks fine 21:32:49 is there a way to edit the minutes? 21:33:01 misspelled words, typos, etc? 21:33:06 I usually don'tbother 21:33:31 okay cool 21:35:54 rrsagent, set logs public-visible 21:36:56 abarth has joined #webappsec 21:37:35 SEC_WASWG()5:00PM has now started 21:37:41 +abarth 21:38:10 i guess you all ended early 21:38:18 yeah, we finished at 2:30 21:38:44 -abarth 21:38:45 SEC_WASWG()5:00PM has ended 21:38:45 Attendees were abarth 21:39:01 abarth: http://www.w3.org/2012/09/25-webappsec-minutes.html 21:39:06 i dont know what's up with Zakim 21:39:20 i'm going to dismiss him. 21:39:23 Zakim, please part 21:39:23 Zakim has left #webappsec