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
wycats's profile
Yehuda Katz 🥨
Yehuda Katz 🥨
Yehuda Katz  🥨
Verified account
@wycats

Tweets

Yehuda Katz  🥨Verified account

@wycats

Tilde Co-Founder, OSS enthusiast and world traveler.

Portland, OR
yehudakatz.com
Joined August 2007

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. Yehuda Katz  🥨‏Verified account @wycats Jan 3

      I've worked on multiple CSRF mitigations in my time on the Rails security team and if GET requests are really now vulnerable to the extent that Google is suggesting using randomized URLs or CSRF tokens, this shit is about to get real.

      1 reply 14 retweets 70 likes
      Show this thread
    2. Yehuda Katz  🥨‏Verified account @wycats Jan 3

      To state the obvious, you cannot use CSRF tokens in URLs and also have those links work as normal links from other web sites.

      2 replies 7 retweets 41 likes
      Show this thread
    3. Yehuda Katz  🥨‏Verified account @wycats Jan 3

      This means that using the same URL for multiple logged-in users becomes a no-no. Again, to state the obvious, this means that I can't share the same URL for a tweet with you if that URL displays personalized content for logged in users.

      5 replies 12 retweets 45 likes
      Show this thread
    4. Yehuda Katz  🥨‏Verified account @wycats Jan 3

      I might be misreading what Google is saying here, but this seems like a significant implication if true.

      12 replies 6 retweets 60 likes
      Show this thread
    5. Sasha Aickin‏ @xander76 Jan 3
      Replying to @wycats

      I read it the same way, and, yeah, this has enormous implications for the personalized web.

      1 reply 0 retweets 4 likes
    6. Sasha Aickin‏ @xander76 Jan 3
      Replying to @xander76 @wycats

      I think rel=canonical may help mitigate some badness; I think I read recently that browsers are starting to use the canonical url when you click the share button.

      1 reply 0 retweets 1 like
    7. Yehuda Katz  🥨‏Verified account @wycats Jan 3
      Replying to @xander76

      I don't see how it helps. You need a single URL to stick on social media, but you want the response to that GET to include personalized content.

      2 replies 0 retweets 1 like
    8. Sasha Aickin‏ @xander76 Jan 3
      Replying to @wycats

      Oh yeah, you're right. I'm not thinking through the scenarios correctly, and it's been quite a while since I've thought one of these through.

      1 reply 0 retweets 2 likes
    9. Yehuda Katz  🥨‏Verified account @wycats Jan 3
      Replying to @xander76

      If this thread model holds, I suspect that the only solution is to fix (on probably some kind of opt in basis) the same origin holes that allow third party sites to make these GET requests in the first place.

      1 reply 0 retweets 2 likes
    10. Sasha Aickin‏ @xander76 Jan 3
      Replying to @wycats

      Isn't that any use of cross-site anything that might load the resource into memory? It's hard for me to imagine a functioning web where GETs of cross-site scripts, images, etc. was disallowed. Or am I misunderstanding again?

      3 replies 0 retweets 0 likes
      Yehuda Katz  🥨‏Verified account @wycats Jan 3
      Replying to @xander76

      It's too late for me to think through all of the threats and apply the new vulnerabilities to them, but you may be right that it's fundamental.

      11:40 PM - 3 Jan 2018
      • 1 Like
      • Sasha Aickin
      2 replies 0 retweets 1 like
        1. Yehuda Katz  🥨‏Verified account @wycats Jan 3
          Replying to @wycats @xander76

          On the "bright" side, the disclosure paper by Project Zero is pretty readable and offers a decent intuition for what's happening.

          0 replies 0 retweets 1 like
          Thanks. Twitter will use this to make your timeline better. Undo
          Undo
        1. New conversation
        2. Sasha Aickin‏ @xander76 Jan 3
          Replying to @wycats

          100% Fair. It's all so overwhelming.

          1 reply 0 retweets 1 like
        3. Yehuda Katz  🥨‏Verified account @wycats Jan 3
          Replying to @xander76

          We probably need to work it out in a matter of days, even with the browser mitigations. I'm not on the Rails security team anymore but I hope they're looking into this ASAP.

          0 replies 0 retweets 1 like
        4. 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