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. Sebastian Lekies‏ @slekies 28 Jan 2017
      Replying to @arturjanc @sirdarckcat @mikewest

      I was thinking more about the default behavior. But if security is inconvenient, no one will adopt it.

      2 replies 0 retweets 0 likes
    2. Eduardo Vela‏ @sirdarckcat 28 Jan 2017
      Replying to @slekies @arturjanc @mikewest

      FWs will want to *work* when developers "turn on" security features. So they will work around them. Simple.

      1 reply 0 retweets 0 likes
    3. Artur Janc‏ @arturjanc 28 Jan 2017
      Replying to @sirdarckcat @slekies @mikewest

      And if they do they will be wrong, and detrimental to user security. Luckily it's a fixable problem.

      1 reply 0 retweets 1 like
    4. Eduardo Vela‏ @sirdarckcat 28 Jan 2017
      Replying to @arturjanc @slekies @mikewest

      is ng-csp detrimental to user security?

      1 reply 0 retweets 0 likes
    5. Artur Janc‏ @arturjanc 28 Jan 2017
      Replying to @sirdarckcat @slekies @mikewest

      Yes, the Angular security model based on bypassing platform security features (via {{ }} and AST*) is wrong

      2 replies 0 retweets 1 like
    6. Artur Janc‏ @arturjanc 28 Jan 2017
      Replying to @arturjanc @sirdarckcat and

      ... and is the source of countless vulnerabilities we otherwise wouldn't have. We can't let it happen again.

      1 reply 0 retweets 2 likes
    7. Artur Janc‏ @arturjanc 28 Jan 2017
      Replying to @arturjanc @sirdarckcat and

      Also, saying that hardening APIs is bad because "frameworks can work around it" is incredibly short-sighted.

      1 reply 0 retweets 4 likes
    8. Sebastian Lekies‏ @slekies 28 Jan 2017
      Replying to @arturjanc @sirdarckcat @mikewest

      I am not saying that at all. Just saying we need to take this into account to not get it wrong.

      1 reply 0 retweets 0 likes
    9. Sebastian Lekies‏ @slekies 28 Jan 2017
      Replying to @slekies @arturjanc and

      I can show you dozens of examples where the current behavior of innerHTML led to hacks in libraries.

      3 replies 0 retweets 0 likes
    10. Sebastian Lekies‏ @slekies 28 Jan 2017
      Replying to @slekies @arturjanc and

      every single one is a CSP bypass btw

      1 reply 0 retweets 0 likes
      Artur Janc‏ @arturjanc 28 Jan 2017
      Replying to @slekies @sirdarckcat @mikewest

      Not really; it's incompatible with one particular way to do CSP ('strict-dynamic') and is easy to fix.

      8:53 AM - 28 Jan 2017
      1 reply 0 retweets 0 likes
        1. New conversation
        2. Sebastian Lekies‏ @slekies 28 Jan 2017
          Replying to @arturjanc @sirdarckcat @mikewest

          not only strict-dynamic, also unsafe-eval, which is required for most frameworks.

          1 reply 0 retweets 0 likes
        3. Sebastian Lekies‏ @slekies 28 Jan 2017
          Replying to @slekies @arturjanc and

          and it is not easy to fix ;-).

          3 replies 0 retweets 0 likes
        4. Artur Janc‏ @arturjanc 28 Jan 2017
          Replying to @slekies @sirdarckcat @mikewest

          You're right, it isn't, there are no easy solutions to complex problems. But hardened core APIs are a start.

          1 reply 0 retweets 0 likes
        5. Sebastian Lekies‏ @slekies 28 Jan 2017
          Replying to @arturjanc @sirdarckcat @mikewest

          yes, definetly. I am the last one to argue against hardening. Just brought up one important issue.

          1 reply 0 retweets 0 likes
        6. Artur Janc‏ @arturjanc 28 Jan 2017
          Replying to @slekies @sirdarckcat @mikewest

          Our disagreement boils down to the question of whether we can get FWs to play nice with new, hardened APIs.

          2 replies 0 retweets 0 likes
        7. Artur Janc‏ @arturjanc 28 Jan 2017
          Replying to @arturjanc @slekies and

          If we can't then we can never put faith in secure APIs for the web b/c they can always be subverted by FWs.

          1 reply 0 retweets 0 likes
        8. Sebastian Lekies‏ @slekies 28 Jan 2017
          Replying to @arturjanc @sirdarckcat @mikewest

          again:I am not saying we can't do this.I am not at all oposing the idea. Just saying we need to be careful

          1 reply 0 retweets 0 likes
        9. Artur Janc‏ @arturjanc 28 Jan 2017
          Replying to @slekies @sirdarckcat @mikewest

          Violent agreement, then? :) FWIW we've done a bad job at secure-by-default JS FWs and we should get better.

          1 reply 0 retweets 0 likes
        10. 1 more reply

      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