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. koto‏ @kkotowicz May 20

      koto Retweeted Roman Shafigullin

      Great talk by @0x6D6172696F. I agree 99%, for the 1% see comment.https://twitter.com/shafigullin/status/998117117726670849 …

      koto added,

      Roman Shafigullin @shafigullin
      @0x6D6172696F https://youtu.be/9dCvcq7KkxA 
      1 reply 10 retweets 31 likes
      Show this thread
    2. koto‏ @kkotowicz May 20

      XSS can only be fixed scalably by pushing the fixes down the stack - to libs, linters, and finally the platform. That has to add complexity, but is the only viable way. With skill that complexity can be inflicted on sec folks, not developers.

      2 replies 4 retweets 19 likes
      Show this thread
    3. John Wilander‏ @johnwilander May 20
      Replying to @kkotowicz @arturjanc

      It can also be fixed by first-party-only scripting plus file-only scripting. First party would include [first party eTLD+1 without dot].[cdn registered as public suffix] domains.

      2 replies 0 retweets 0 likes
      Artur Janc‏ @arturjanc May 20
      Replying to @johnwilander @kkotowicz

      Unfortunately there's very little chance of this working. CSP tried getting developrs to remove inline <script>s and failed miserably, for a myriad of reasons.

      10:36 AM - 20 May 2018
      • 1 Retweet
      • 4 Likes
      • superspooktacular isogenies koto Yoav Weiss Ryan Sleevi
      1 reply 1 retweet 4 likes
        1. New conversation
        2. John Wilander‏ @johnwilander May 20
          Replying to @arturjanc @kkotowicz

          The vague carrot of “you may not be hacked” plus complexity killed CSP. Next try should apply more stick. The web as a platform for business, communication etc. deserves much better than XSS whack-a-mole because developers want inline scripts. Tragedy of the commons.

          1 reply 0 retweets 2 likes
        3. koto‏ @kkotowicz May 20
          Replying to @johnwilander @arturjanc

          You're proposing an app store that happens to use http. That's not the web platform.

          1 reply 0 retweets 3 likes
        4. John Wilander‏ @johnwilander May 20
          Replying to @kkotowicz @arturjanc

          That’s not what I’m proposing at all. I merely propose that websites only run their own code.

          1 reply 0 retweets 1 like
        5. koto‏ @kkotowicz May 20
          Replying to @johnwilander @arturjanc

          The web has that feature - it's script-src self (+whitelists for the site/etld+1). It's opt in, and the adoption rate is poor for many reasons. Mandating it seems like a very difficult task, as very few authors would want to have such limitations.

          1 reply 0 retweets 2 likes
        6. John Wilander‏ @johnwilander May 20
          Replying to @kkotowicz @arturjanc

          That is the tragedy of the commons. Developers want the freedom but not the consequences. Endusers are deceived and pay the price. We can do something about it.

          2 replies 0 retweets 1 like
        7. koto‏ @kkotowicz May 20
          Replying to @johnwilander @arturjanc

          XSS, for the most part, is not caused by distributed code loading in your app. It lurks in a total codebase complexity of modern apps, and a lack of safe defaults. Changing domain names does not solve XSS.

          3 replies 3 retweets 6 likes
        8. John Wilander‏ @johnwilander May 20
          Replying to @kkotowicz @arturjanc

          I believe you’re talking about bugs. I’m talking about what scripts get executed. Only files and only from your domain or from one chosen CDN with your own eTLD+1 scope and checked through SRI. Any other script will not be executed.

          1 reply 0 retweets 0 likes
        9. Damned Whey-pits‏ @dveditz May 20
          Replying to @johnwilander @kkotowicz @arturjanc

          Yes, koto started the thread talking about XSS which is a class of bugs. You're talking about intentional 3rd party scripts. That's not XSS. Unlikely to go away unless we find a non-advertising model for the web.

          2 replies 0 retweets 5 likes
        10. 6 more replies

      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