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. Colm MacCárthaigh‏ @colmmacc 26 Mar 2018
      • Report Tweet
      • Report NetzDG Violation

      Now the TLS1.3 people are still like BUT WE WANT SPEED, SO JUST DEAL WITH IT. And the distributed systems people are like IDEMPOTENCY IS REALLY HARD, WE MEAN IT. But wait, it turns out that we can actually get anti-replay and forward secrecy back, and keep 0-RTT, how ....

      1 reply 0 retweets 27 likes
      Show this thread
    2. Colm MacCárthaigh‏ @colmmacc 26 Mar 2018
      • Report Tweet
      • Report NetzDG Violation

      The answer is for the server not to use key-in-a-key BS. Instead if the server just remembers the key, let's a client use it ONCE, and deletes it when it's done ... we get FORWARD SECRECY and ANTI-REPLAY. REJOICE!!!

      2 replies 0 retweets 27 likes
      Show this thread
    3. Colm MacCárthaigh‏ @colmmacc 26 Mar 2018
      • Report Tweet
      • Report NetzDG Violation

      .... except it costs the server money. It has to cache more keys, and it's not easy to distribute across wide geographic areas, and comes with its own distributed systems challenges. But guess what? THAT'S ALL THE TLS SERVER'S PROBLEM.

      1 reply 0 retweets 23 likes
      Show this thread
    4. Colm MacCárthaigh‏ @colmmacc 26 Mar 2018
      • Report Tweet
      • Report NetzDG Violation

      ... no need to modify thousands of applications, no need to teach PHP and RubyOnRails developers the intricacies of idempotency edge cases. Nope, just one slightly costly change within the TLS1.3 servers. So that's my plan, and REJOICE again, because TLS1.3 can have secure 0-RTT

      1 reply 0 retweets 27 likes
      Show this thread
    5. Colm MacCárthaigh‏ @colmmacc 26 Mar 2018
      • Report Tweet
      • Report NetzDG Violation

      .... unless some TLS servers would cut corners, and just want the fast benchmarks, and you know .... deploy TLS1.3 0-RTT without built-in SAFETY mechanisms. That would be INSANE, I mean, why risk bugs and side-channels, right?

      2 replies 4 retweets 31 likes
      Show this thread
    6. Colm MacCárthaigh‏ @colmmacc 26 Mar 2018
      • Report Tweet
      • Report NetzDG Violation

      Oh right, no that's exactly what's happening. So here's my advice: if you see a server supporting 0-RTT and that server doesn't give you an iron-clad guarantee that when the key is used, it's deleted, and that your EARLY CONVERSATION can't be repeated ... don't use it.

      6 replies 21 retweets 79 likes
      Show this thread
    7. Colm MacCárthaigh‏ @colmmacc 26 Mar 2018
      • Report Tweet
      • Report NetzDG Violation

      Last message in the thread: no 0-RTT is not some NSA backdoor (Dear HN: grow up), there are no intentional back doors in TLS1.3, and it is still overall AWESOME AND EXCITING and we'll be adding it to s2n ... VERY SOON. EOF.

      6 replies 6 retweets 89 likes
      Show this thread
    8. This Tweet is unavailable.
    9. Colm MacCárthaigh‏ @colmmacc 26 Mar 2018
      • Report Tweet
      • Report NetzDG Violation

      Once I saw DANE I lost interest, DNSSEC is train wreck awful. Do not use.

      1 reply 0 retweets 1 like
    10. Viktor Dukhovni‏ @VDukhovni 27 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @colmmacc

      Smug FUD mongering is fun, but harmful. You really should find a better pastime. Read RFC7435, and think about why good enough security is better than none. Ciao.

      2 replies 0 retweets 0 likes
      Colm MacCárthaigh‏ @colmmacc 28 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @VDukhovni

      No FUD! DNSSEC doesn't provide secrecy, anti-replay, or even anti-forgery in practice. If it /just/ did nothing it might be an ok experiment, but it also causes real outages due to complexity, and makes DDOSes worse. That makes it not a good idea.

      3:17 PM - 28 Mar 2018
      1 reply 0 retweets 0 likes
        1. New conversation
        2. Matthew Hardeman‏ @mdhardeman 28 Mar 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @colmmacc @VDukhovni

          Now I'm falling into a DNSSEC hole. I agree on no secrecy and no anti-replay. Is it really not useful against anti-forgery? If not, why not? I don't see the issue other than some questionable key size/alg decisions which should get resolved over time. Am I missing something?

          1 reply 0 retweets 0 likes
        3. Colm MacCárthaigh‏ @colmmacc 28 Mar 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @mdhardeman @VDukhovni

          Absolutely! 1/ DNSSEC does *nothing* between your Browser/computer and your resolver. But that's the weakest link! 2/ For other links, junk crypto like RSA-512 with SHA1 is still common. I can break that on my watch.

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

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