public-web-security@w3.org from January 2011 by thread

[Content Security Policy] A more modular approach Brandon Sterne (Monday, 31 January)

Re: CSP XML Data with tokens gaz Heyes (Thursday, 27 January)

• Re: CSP XML Data with tokens Devdatta Akhawe (Thursday, 27 January)
  • Re: CSP XML Data with tokens sird@rckc.at (Friday, 28 January)
    • Re: CSP XML Data with tokens sird@rckc.at (Friday, 28 January)
      • Re: CSP XML Data with tokens Devdatta Akhawe (Friday, 28 January)
        • Re: CSP XML Data with tokens Devdatta Akhawe (Friday, 28 January)
          • Re: CSP XML Data with tokens sird@rckc.at (Friday, 28 January)
            • Re: CSP XML Data with tokens gaz Heyes (Friday, 28 January)
            • Re: CSP XML Data with tokens sird@rckc.at (Friday, 28 January)
            • Re: CSP XML Data with tokens sird@rckc.at (Friday, 28 January)
            • Re: CSP XML Data with tokens gaz Heyes (Friday, 28 January)
            • Re: CSP XML Data with tokens Adam Barth (Friday, 28 January)
            • Re: CSP XML Data with tokens gaz Heyes (Friday, 28 January)
            • Re: CSP XML Data with tokens sird@rckc.at (Friday, 28 January)
            • Re: CSP XML Data with tokens gaz Heyes (Friday, 28 January)
            • Re: CSP XML Data with tokens sird@rckc.at (Friday, 28 January)
            • Re: CSP XML Data with tokens gaz Heyes (Saturday, 29 January)
            • Re: CSP XML Data with tokens sird@rckc.at (Saturday, 29 January)
            • Re: CSP XML Data with tokens Gareth Heyes (Saturday, 29 January)
            • Re: CSP XML Data with tokens Adam Barth (Saturday, 29 January)
            • Re: CSP XML Data with tokens sird@rckc.at (Sunday, 30 January)
            • Re: CSP XML Data with tokens Michal Zalewski (Sunday, 30 January)
            • Re: CSP XML Data with tokens Adam Barth (Sunday, 30 January)
            • Re: CSP XML Data with tokens Giorgio Maone (Sunday, 30 January)
            • Re: CSP XML Data with tokens Adam Barth (Sunday, 30 January)
            • Re: CSP XML Data with tokens Giorgio Maone (Sunday, 30 January)
            • Re: CSP XML Data with tokens Adam Barth (Sunday, 30 January)
            • Re: CSP XML Data with tokens sird@rckc.at (Sunday, 30 January)
            • Re: CSP XML Data with tokens sird@rckc.at (Sunday, 30 January)
            • Re: CSP XML Data with tokens Michal Zalewski (Sunday, 30 January)
            • Re: CSP XML Data with tokens sird@rckc.at (Monday, 31 January)
            • Re: CSP XML Data with tokens Michal Zalewski (Monday, 31 January)
            • Re: CSP XML Data with tokens Michal Zalewski (Monday, 31 January)
            • Re: CSP XML Data with tokens sird@rckc.at (Monday, 31 January)
            • Re: CSP XML Data with tokens sird@rckc.at (Monday, 31 January)
            • Re: CSP XML Data with tokens gaz Heyes (Monday, 31 January)
            • Re: CSP XML Data with tokens sird@rckc.at (Monday, 31 January)
            • Re: CSP XML Data with tokens Aryeh Gregor (Sunday, 30 January)
            • Re: CSP XML Data with tokens Michal Zalewski (Sunday, 30 January)
      • Re: CSP XML Data with tokens Michal Zalewski (Friday, 28 January)

[Content Security Policy] Proposal to move the debate forward Brandon Sterne (Thursday, 27 January)

• Re: [Content Security Policy] Proposal to move the debate forward Gervase Markham (Thursday, 27 January)
  • Re: [Content Security Policy] Proposal to move the debate forward gaz Heyes (Thursday, 27 January)
  • Re: [Content Security Policy] Proposal to move the debate forward gaz Heyes (Friday, 28 January)
    • Re: [Content Security Policy] Proposal to move the debate forward Gervase Markham (Friday, 28 January)
      • Re: [Content Security Policy] Proposal to move the debate forward gaz Heyes (Friday, 28 January)
        • Re: [Content Security Policy] Proposal to move the debate forward Gervase Markham (Friday, 28 January)
          • Re: [Content Security Policy] Proposal to move the debate forward gaz Heyes (Friday, 28 January)
            • Re: [Content Security Policy] Proposal to move the debate forward Gervase Markham (Friday, 28 January)
            • Re: [Content Security Policy] Proposal to move the debate forward gaz Heyes (Friday, 28 January)
            • Re: [Content Security Policy] Proposal to move the debate forward Gervase Markham (Friday, 28 January)
            • Re: [Content Security Policy] Proposal to move the debate forward gaz Heyes (Friday, 28 January)
            • Re: [Content Security Policy] Proposal to move the debate forward gaz Heyes (Friday, 28 January)
            • Re: [Content Security Policy] Proposal to move the debate forward Brandon Sterne (Friday, 28 January)
            • Re: [Content Security Policy] Proposal to move the debate forward gaz Heyes (Friday, 28 January)
            • Re: [Content Security Policy] Proposal to move the debate forward Brandon Sterne (Friday, 28 January)
            • Re: [Content Security Policy] Proposal to move the debate forward gaz Heyes (Friday, 28 January)
            • Re: [Content Security Policy] Proposal to move the debate forward Brandon Sterne (Friday, 28 January)
            • Re: [Content Security Policy] Proposal to move the debate forward gaz Heyes (Saturday, 29 January)
            • Re: [Content Security Policy] Proposal to move the debate forward Gervase Markham (Monday, 31 January)
            • Re: [Content Security Policy] Proposal to move the debate forward Michal Zalewski (Monday, 31 January)
            • Re: [Content Security Policy] Proposal to move the debate forward Michal Zalewski (Monday, 31 January)
            • Re: [Content Security Policy] Proposal to move the debate forward gaz Heyes (Monday, 31 January)
• Re: [Content Security Policy] Proposal to move the debate forward Michal Zalewski (Thursday, 27 January)
  • Re: [Content Security Policy] Proposal to move the debate forward Daniel Veditz (Thursday, 27 January)
    • Re: [Content Security Policy] Proposal to move the debate forward Adam Barth (Thursday, 27 January)
      • Re: [Content Security Policy] Proposal to move the debate forward Daniel Veditz (Thursday, 27 January)
    • Re: [Content Security Policy] Proposal to move the debate forward Gervase Markham (Friday, 28 January)
• Re: [Content Security Policy] Proposal to move the debate forward Adam Barth (Thursday, 27 January)
  • Re: [Content Security Policy] Proposal to move the debate forward Boris Zbarsky (Thursday, 27 January)
  • Re: [Content Security Policy] Proposal to move the debate forward Michal Zalewski (Thursday, 27 January)
    • Re: [Content Security Policy] Proposal to move the debate forward Adam Barth (Thursday, 27 January)
  • Re: [Content Security Policy] Proposal to move the debate forward Gervase Markham (Friday, 28 January)
    • Re: [Content Security Policy] Proposal to move the debate forward Adam Barth (Friday, 28 January)
      • Re: [Content Security Policy] Proposal to move the debate forward Boris Zbarsky (Friday, 28 January)
        • Re: [Content Security Policy] Proposal to move the debate forward Adam Barth (Friday, 28 January)
          • Re: [Content Security Policy] Proposal to move the debate forward Michal Zalewski (Friday, 28 January)
          • Re: [Content Security Policy] Proposal to move the debate forward Boris Zbarsky (Friday, 28 January)
            • Re: [Content Security Policy] Proposal to move the debate forward Adam Barth (Friday, 28 January)
        • Re: [Content Security Policy] Proposal to move the debate forward robert@webappsec.org (Friday, 28 January)
      • Re: [Content Security Policy] Proposal to move the debate forward Lucas Adamski (Monday, 31 January)
        • Re: [Content Security Policy] Proposal to move the debate forward Adam Barth (Monday, 31 January)
          • Re: [Content Security Policy] Proposal to move the debate forward Gervase Markham (Monday, 31 January)
            • Re: [Content Security Policy] Proposal to move the debate forward Adam Barth (Monday, 31 January)
• Re: [Content Security Policy] Proposal to move the debate forward Devdatta Akhawe (Thursday, 27 January)
  • Re: [Content Security Policy] Proposal to move the debate forward Michal Zalewski (Thursday, 27 January)
    • Re: [Content Security Policy] Proposal to move the debate forward gaz Heyes (Thursday, 27 January)
      • Re: [Content Security Policy] Proposal to move the debate forward Michal Zalewski (Thursday, 27 January)
• Re: [Content Security Policy] Proposal to move the debate forward gaz Heyes (Friday, 28 January)
  • Re: [Content Security Policy] Proposal to move the debate forward Brandon Sterne (Friday, 28 January)
    • Re: [Content Security Policy] Proposal to move the debate forward gaz Heyes (Friday, 28 January)
      • Re: [Content Security Policy] Proposal to move the debate forward Brandon Sterne (Friday, 28 January)
        • Re: [Content Security Policy] Proposal to move the debate forward gaz Heyes (Friday, 28 January)
          • Re: [Content Security Policy] Proposal to move the debate forward Brandon Sterne (Friday, 28 January)
            • Re: [Content Security Policy] Proposal to move the debate forward gaz Heyes (Saturday, 29 January)
            • Re: [Content Security Policy] Proposal to move the debate forward Daniel Veditz (Sunday, 30 January)
            • Re: [Content Security Policy] Proposal to move the debate forward Aryeh Gregor (Sunday, 30 January)
            • Re: [Content Security Policy] Proposal to move the debate forward Lucas Adamski (Monday, 31 January)
            • [Content Security Policy] Usability? Terri Oda (Sunday, 30 January)
            • Re: [Content Security Policy] Proposal to move the debate forward Gervase Markham (Monday, 31 January)
            • Re: [Content Security Policy] Proposal to move the debate forward gaz Heyes (Monday, 31 January)
            • Re: [Content Security Policy] Proposal to move the debate forward Gervase Markham (Monday, 31 January)

Policy syntax (was Re: Scope and complexity) Adam Barth (Tuesday, 25 January)

Scope and complexity (was Re: More on XSS mitigation) Adam Barth (Monday, 24 January)

• Re: Scope and complexity (was Re: More on XSS mitigation) Gervase Markham (Tuesday, 25 January)
  • RE: Scope and complexity (was Re: More on XSS mitigation) Steingruebl, Andy (Tuesday, 25 January)
  • Re: Scope and complexity (was Re: More on XSS mitigation) Adam Barth (Tuesday, 25 January)
    • Re: Scope and complexity (was Re: More on XSS mitigation) Brandon Sterne (Tuesday, 25 January)
    • Re: Scope and complexity (was Re: More on XSS mitigation) Lucas Adamski (Tuesday, 25 January)
    • Re: Scope and complexity (was Re: More on XSS mitigation) Brandon Sterne (Tuesday, 25 January)
      • Re: Scope and complexity (was Re: More on XSS mitigation) Adam Barth (Tuesday, 25 January)
        • Re: Scope and complexity (was Re: More on XSS mitigation) gaz Heyes (Tuesday, 25 January)
        • Re: Scope and complexity (was Re: More on XSS mitigation) Brandon Sterne (Tuesday, 25 January)
          • Re: Scope and complexity (was Re: More on XSS mitigation) Adam Barth (Tuesday, 25 January)
            • Re: Scope and complexity (was Re: More on XSS mitigation) Boris Zbarsky (Tuesday, 25 January)
            • Re: Scope and complexity (was Re: More on XSS mitigation) Brandon Sterne (Tuesday, 25 January)
            • Re: Scope and complexity (was Re: More on XSS mitigation) Adam Barth (Tuesday, 25 January)
• Re: Scope and complexity (was Re: More on XSS mitigation) Daniel Veditz (Tuesday, 25 January)
• Re: Scope and complexity (was Re: More on XSS mitigation) Lucas Adamski (Tuesday, 25 January)

More on XSS mitigation (was Re: XSS mitigation in browsers) Adam Barth (Friday, 21 January)

• Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Michal Zalewski (Friday, 21 January)
  • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Adam Barth (Friday, 21 January)
    • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Michal Zalewski (Friday, 21 January)
      • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Adam Barth (Saturday, 22 January)
        • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Michal Zalewski (Saturday, 22 January)
          • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Adam Barth (Saturday, 22 January)
            • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Devdatta Akhawe (Saturday, 22 January)
  • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Daniel Veditz (Saturday, 22 January)
    • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Adam Barth (Saturday, 22 January)
      • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Daniel Veditz (Saturday, 22 January)
        • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Adam Barth (Saturday, 22 January)
  • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Gervase Markham (Saturday, 22 January)
    • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Michal Zalewski (Saturday, 22 January)
      • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Adam Barth (Saturday, 22 January)
    • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) gaz Heyes (Saturday, 22 January)
      • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Michal Zalewski (Saturday, 22 January)
        • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) John Wilander (Monday, 24 January)
          • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Adam Barth (Monday, 24 January)
          • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Devdatta Akhawe (Monday, 24 January)
            • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Gervase Markham (Monday, 24 January)
            • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Brandon Sterne (Monday, 24 January)
            • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) gaz Heyes (Monday, 24 January)
            • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Adam Barth (Monday, 24 January)
            • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Adam Barth (Monday, 24 January)
            • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Joel H. W. Weinberger (Wednesday, 26 January)
          • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Henrik Nordström (Monday, 24 January)
          • Re: More on XSS mitigation (was Re: XSS mitigation in browsers) John Wilander (Monday, 24 January)
• Re: More on XSS mitigation (was Re: XSS mitigation in browsers) Lucas Adamski (Friday, 21 January)

wrt coming up with unified frameworks (was: Re: XSS mitigation in browsers) =JeffH (Friday, 21 January)

XSS mitigation in browsers Adam Barth (Wednesday, 19 January)

• Re: XSS mitigation in browsers sird@rckc.at (Wednesday, 19 January)
  • Re: XSS mitigation in browsers Adam Barth (Wednesday, 19 January)
    • Re: XSS mitigation in browsers sird@rckc.at (Wednesday, 19 January)
      • Re: XSS mitigation in browsers sird@rckc.at (Wednesday, 19 January)
        • Re: XSS mitigation in browsers Adam Barth (Wednesday, 19 January)
    • Re: XSS mitigation in browsers Giorgio Maone (Wednesday, 19 January)
      • Re: XSS mitigation in browsers Adam Barth (Thursday, 20 January)
        • Re: XSS mitigation in browsers Michal Zalewski (Thursday, 20 January)
• Re: XSS mitigation in browsers Michal Zalewski (Wednesday, 19 January)
  • Re: XSS mitigation in browsers Adam Barth (Wednesday, 19 January)
    • Re: XSS mitigation in browsers Michal Zalewski (Wednesday, 19 January)
  • Re: XSS mitigation in browsers Daniel Veditz (Saturday, 22 January)
• Re: XSS mitigation in browsers gaz Heyes (Thursday, 20 January)
• Re: XSS mitigation in browsers Boris Zbarsky (Thursday, 20 January)
• Re: XSS mitigation in browsers Brandon Sterne (Thursday, 20 January)
  • Re: XSS mitigation in browsers Michal Zalewski (Thursday, 20 January)
    • Re: XSS mitigation in browsers Michal Zalewski (Thursday, 20 January)
      • Re: XSS mitigation in browsers gaz Heyes (Thursday, 20 January)
        • Re: XSS mitigation in browsers Michal Zalewski (Thursday, 20 January)
      • Re: XSS mitigation in browsers Lucas Adamski (Friday, 21 January)
        • RE: XSS mitigation in browsers Steingruebl, Andy (Monday, 24 January)
      • Re: XSS mitigation in browsers Sid Stamm (Thursday, 20 January)
        • Re: XSS mitigation in browsers Michal Zalewski (Thursday, 20 January)
        • Re: XSS mitigation in browsers Michal Zalewski (Thursday, 20 January)
          • Re: XSS mitigation in browsers gaz Heyes (Thursday, 20 January)
            • Re: XSS mitigation in browsers sird@rckc.at (Friday, 21 January)
            • Re: XSS mitigation in browsers sird@rckc.at (Friday, 21 January)
            • Re: XSS mitigation in browsers Boris Zbarsky (Friday, 21 January)
            • Re: XSS mitigation in browsers Boris Zbarsky (Friday, 21 January)
            • Re: XSS mitigation in browsers gaz Heyes (Friday, 21 January)
      • RE: XSS mitigation in browsers Steingruebl, Andy (Thursday, 20 January)
        • Re: XSS mitigation in browsers Michal Zalewski (Friday, 21 January)
          • RE: XSS mitigation in browsers Steingruebl, Andy (Friday, 21 January)
            • Re: XSS mitigation in browsers Collin Jackson (Monday, 24 January)
            • Re: XSS mitigation in browsers Devdatta Akhawe (Monday, 24 January)
            • Re: XSS mitigation in browsers Boris Zbarsky (Monday, 24 January)
  • Re: XSS mitigation in browsers gaz Heyes (Thursday, 20 January)
    • Re: XSS mitigation in browsers Giorgio Maone (Thursday, 20 January)
  • Re: XSS mitigation in browsers Daniel Veditz (Friday, 21 January)
    • Re: XSS mitigation in browsers Michal Zalewski (Friday, 21 January)
      • Re: XSS mitigation in browsers Michal Zalewski (Friday, 21 January)
      • Re: XSS mitigation in browsers Daniel Veditz (Friday, 21 January)
      • Re: XSS mitigation in browsers Giorgio Maone (Friday, 21 January)
        • Re: XSS mitigation in browsers gaz Heyes (Friday, 21 January)
          • Re: XSS mitigation in browsers Michal Zalewski (Friday, 21 January)
            • Re: XSS mitigation in browsers Michal Zalewski (Friday, 21 January)
            • Re: XSS mitigation in browsers gaz Heyes (Friday, 21 January)
            • Re: XSS mitigation in browsers Michal Zalewski (Friday, 21 January)
            • Re: XSS mitigation in browsers gaz Heyes (Friday, 21 January)
            • Re: XSS mitigation in browsers Michal Zalewski (Friday, 21 January)
            • Re: XSS mitigation in browsers Devdatta Akhawe (Friday, 21 January)
            • Re: XSS mitigation in browsers Michal Zalewski (Friday, 21 January)
            • Re: XSS mitigation in browsers Daniel Veditz (Friday, 21 January)
            • Re: XSS mitigation in browsers Daniel Veditz (Friday, 21 January)
            • Re: XSS mitigation in browsers Michal Zalewski (Friday, 21 January)
            • Re: XSS mitigation in browsers Daniel Veditz (Saturday, 22 January)
            • Re: XSS mitigation in browsers Michal Zalewski (Saturday, 22 January)
            • Re: XSS mitigation in browsers Lucas Adamski (Friday, 21 January)
            • Re: XSS mitigation in browsers Adam Barth (Saturday, 22 January)
            • Re: XSS mitigation in browsers Lucas Adamski (Wednesday, 26 January)
            • Re: XSS mitigation in browsers Gervase Markham (Saturday, 22 January)
            • Re: XSS mitigation in browsers Devdatta Akhawe (Saturday, 22 January)
            • Re: XSS mitigation in browsers Adam Barth (Saturday, 22 January)
            • Re: XSS mitigation in browsers Devdatta Akhawe (Saturday, 22 January)
            • Re: XSS mitigation in browsers Adam Barth (Saturday, 22 January)
            • Re: XSS mitigation in browsers Daniel Veditz (Saturday, 22 January)
          • Re: XSS mitigation in browsers Henrich C. Pöhls (Friday, 21 January)
  • Re: XSS mitigation in browsers Thomas Roessler (Friday, 21 January)

[W2SP] Web 2.0 Security and Privacy 2011 Workshop - Call for Papers Larry Koved (Tuesday, 18 January)

Web 2.0 Security and Privacy 2011 Workshop CFP Thomas Roessler (Monday, 17 January)

Last message date: Monday, 31 January 2011 23:00:32 UTC