Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.
  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
arturjanc's profile
Artur Janc
Artur Janc
Artur Janc
@arturjanc

Tweets

Artur Janc

@arturjanc

Making the web platform more secure one Twitter flamewar at a time.

Zurich, Switzerland
Joined February 2012

Tweets

  • © 2018 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. Mike West‏ @mikewest 5 Oct 2017
      Replying to @slekies @intenttoship

      Talk to @arturjanc.

      2 replies 0 retweets 0 likes
    2. Artur Janc‏ @arturjanc 5 Oct 2017
      Replying to @mikewest @slekies @intenttoship

      Yes, it lets apps with lots of static HTML add CSP which will allow existing inline scripts to run, while preventing arbitrary JS execution.

      1 reply 0 retweets 3 likes
    3. Sebastian Lekies‏ @slekies 5 Oct 2017
      Replying to @arturjanc @mikewest @intenttoship

      It also enables new CSRF-like XSS attacks. Developers will use it because its easier than rewriting. Not sure if this is a good idea.

      1 reply 0 retweets 4 likes
    4. Sebastian Lekies‏ @slekies 5 Oct 2017
      Replying to @slekies @arturjanc and

      Do pages whitelist handlers on a per-page basis or do you think there will be one policy containing all handlers of an app?

      1 reply 0 retweets 1 like
    5. Sebastian Lekies‏ @slekies 5 Oct 2017
      Replying to @slekies @arturjanc and

      Also is the attribute name part of the hash?

      1 reply 0 retweets 1 like
    6. Artur Janc‏ @arturjanc 5 Oct 2017
      Replying to @slekies @mikewest @intenttoship

      It's likely going to be a per-page policy generated automatically by middleware for static HTML, allowing only scripts from the current doc.

      1 reply 0 retweets 1 like
    7. Artur Janc‏ @arturjanc 5 Oct 2017
      Replying to @arturjanc @slekies and

      One of the proposals was to include event handler names, but this seems more complicated for little benefit so I'd prefer to avoid it.

      2 replies 0 retweets 1 like
    8. Sebastian Lekies‏ @slekies 5 Oct 2017
      Replying to @arturjanc @mikewest @intenttoship

      It would disable a lot of the code-reuse attack vectors.

      1 reply 0 retweets 1 like
    9. Artur Janc‏ @arturjanc 5 Oct 2017
      Replying to @slekies @mikewest @intenttoship

      For common EHs like onclick, onload, onmouse* this seems tough b/c the attacker controls the DOM and can dupe the user into causing events.

      1 reply 0 retweets 1 like
    10. Sebastian Lekies‏ @slekies 5 Oct 2017
      Replying to @arturjanc @mikewest @intenttoship

      Yes, but it prevents the attacker from reusing an onclick handler in an onload handler.

      1 reply 0 retweets 1 like
      Artur Janc‏ @arturjanc 5 Oct 2017
      Replying to @slekies @mikewest @intenttoship

      The attacker can add a full-page overlay so any click will trigger the `onclick' EH; it's hard to prevent it, IMO not worth trying.

      10:46 AM - 5 Oct 2017
      1 reply 0 retweets 0 likes
        1. New conversation
        2. Sebastian Lekies‏ @slekies 5 Oct 2017
          Replying to @arturjanc @mikewest @intenttoship

          Removing user interaction makes attacks easier. I have more examples, but twitter is not suitable for explaining those.

          1 reply 0 retweets 1 like
        3. Artur Janc‏ @arturjanc 5 Oct 2017
          Replying to @slekies @mikewest @intenttoship

          I agree 💯 and would definitely encourage you to comment on the spec (either one of the GitHub issues linked above, or just start a new one!)

          1 reply 0 retweets 1 like
        4. koto‏ @kkotowicz 9 Oct 2017
          Replying to @arturjanc @slekies and

          If the intention is to automatically apply this, how can you possible address the warning in the spec 8.3? https://w3c.github.io/webappsec-csp/#unsafe-hashed-attributes-usage …

          1 reply 0 retweets 0 likes
        5. Artur Janc‏ @arturjanc 9 Oct 2017
          Replying to @kkotowicz @slekies and

          Applying this to static pages would bless inline scripts present in those pages; on many sites such content is separate from the main app...

          1 reply 0 retweets 0 likes
        6. Artur Janc‏ @arturjanc 9 Oct 2017
          Replying to @arturjanc @kkotowicz and

          In those cases the scripts often do not invoke functions which trigger interesting behavior (in our use cases it's often just analytics).

          1 reply 0 retweets 0 likes
        7. Artur Janc‏ @arturjanc 9 Oct 2017
          Replying to @arturjanc @kkotowicz and

          I hope we can agree that this is not infallible, but it is a significant tightening of the "no restrictions at all" model of 'unsafe-inline'

          1 reply 0 retweets 0 likes
        8. Artur Janc‏ @arturjanc 9 Oct 2017
          Replying to @arturjanc @kkotowicz and

          For apps which are able to easily refactor their inline event handlers, the answer is: just do it. 'u-h-a' is for the 90% who can't/don't.

          1 reply 0 retweets 0 likes
        9. Artur Janc‏ @arturjanc 9 Oct 2017
          Replying to @arturjanc @kkotowicz and

          It also unblocks apps using widgets incompatible with CSP. Now you can often just bless their event handlers and you fix 'unsafe-inline'.

          0 replies 0 retweets 0 likes
        10. End of conversation

      Loading seems to be taking a while.

      Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

        Promoted Tweet

        false

        • © 2018 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Cookies
        • Ads info