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.

This is the legacy version of twitter.com. We will be shutting it down on June 1, 2020. Please switch to a supported browser, or disable the extension which masks your browser. You can see a list of supported browsers in our Help Center.

  • 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
colmmacc's profile
Colm MacCárthaigh
Colm MacCárthaigh
Colm MacCárthaigh
@colmmacc

Tweets

Colm MacCárthaigh

@colmmacc

AWS, Apache, Crypto, Irish Music, Haiku, Photography

Seattle
notesfromthesound.com
Joined April 2008

Tweets

  • © 2020 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Imprint
  • 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. Nick Sullivan‏Verified account @grittygrease 24 Oct 2017
      • Report Tweet
      • Report NetzDG Violation
      Replying to @colmmacc @tqbf

      FS is relative to the secret (STEK vs Privkey). In non-DH resumption, the entire resumed connection is not FS wrt STEK, not just 0-RTT data

      1 reply 0 retweets 0 likes
    2. Colm MacCárthaigh‏ @colmmacc 24 Oct 2017
      • Report Tweet
      • Report NetzDG Violation
      Replying to @grittygrease @tqbf

      In TLS1.3 there is no non-DH resume though, only the 0-RTT data misses FS, but is also the most critical data.

      2 replies 0 retweets 0 likes
    3. Nick Sullivan‏Verified account @grittygrease 24 Oct 2017
      • Report Tweet
      • Report NetzDG Violation
      Replying to @colmmacc @tqbf

      Read section 2.2: "PSKs can be used with (EC)DHE [..] or can be used alone, at the cost of losing forward secrecy for the application data."

      1 reply 0 retweets 1 like
    4. Nick Sullivan‏Verified account @grittygrease 24 Oct 2017
      • Report Tweet
      • Report NetzDG Violation
      Replying to @grittygrease @colmmacc @tqbf

      Adding FS on the resumption with DH is a SHOULD, not a MUST. BoringSSL and NSS support non-FS resumption, for example.

      2 replies 0 retweets 1 like
    5. Colm MacCárthaigh‏ @colmmacc 24 Oct 2017
      • Report Tweet
      • Report NetzDG Violation
      Replying to @grittygrease @tqbf

      Really? OOB PSK with no DH works, makes sense, but resume? KX alg would change across the sessions, which would be bizarrely tolerant.

      1 reply 0 retweets 0 likes
    6. Nick Sullivan‏Verified account @grittygrease 24 Oct 2017
      • Report Tweet
      • Report NetzDG Violation
      Replying to @colmmacc @tqbf

      Allowed and supported. Lets servers opt out of expensive public key ops during resumption.

      1 reply 0 retweets 0 likes
    7. Colm MacCárthaigh‏ @colmmacc 24 Oct 2017
      • Report Tweet
      • Report NetzDG Violation
      Replying to @grittygrease @tqbf

      Seems insane on two fronts: 1/ It's incompatible with a best practice for resume: negotiate as normal and only resume if all params match.

      1 reply 0 retweets 0 likes
    8. Colm MacCárthaigh‏ @colmmacc 24 Oct 2017
      • Report Tweet
      • Report NetzDG Violation
      Replying to @colmmacc @grittygrease @tqbf

      That avoids attacks where the attacker controls the servers choices by swapping tickets. Also means new alg priorities take.

      2 replies 0 retweets 0 likes
    9. Nick Sullivan‏Verified account @grittygrease 24 Oct 2017
      • Report Tweet
      • Report NetzDG Violation
      Replying to @colmmacc @tqbf

      The key share is considered “extra” on resumption, so there is no check that it matches the previous one.

      1 reply 0 retweets 0 likes
    10. Nick Sullivan‏Verified account @grittygrease 24 Oct 2017
      • Report Tweet
      • Report NetzDG Violation
      Replying to @grittygrease @colmmacc @tqbf

      Not saying it’s a great idea (we explicitly disable non-PFS resumption), but it makes your 0-RTT argument seem misdirected.

      1 reply 0 retweets 0 likes
      Colm MacCárthaigh‏ @colmmacc 24 Oct 2017
      • Report Tweet
      • Report NetzDG Violation
      Replying to @grittygrease @tqbf

      Agreed it could actually be "Clearly we don't care about FS that much at all" :) Though I still think 0-RTT is the bigger real world problem

      5:07 PM - 24 Oct 2017
      1 reply 0 retweets 0 likes
        1. New conversation
        2. Nick Sullivan‏Verified account @grittygrease 24 Oct 2017
          • Report Tweet
          • Report NetzDG Violation
          Replying to @colmmacc @tqbf

          Let’s check back on this when server deployment is high enough that you can measure the % of 0-RTT vs the % of non-FS resumption support.

          1 reply 0 retweets 0 likes
        3. Nick Sullivan‏Verified account @grittygrease 24 Oct 2017
          • Report Tweet
          • Report NetzDG Violation
          Replying to @grittygrease @colmmacc @tqbf

          I smell an IMC paper for @_aaspring_ and @zakirbpd

          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

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