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 18 Oct 2018
      • Report Tweet
      • Report NetzDG Violation

      This looks silly, and there's been knock knock jokes, but it's actually hard to catch with a code review and it's not an uncommon kind of problem. A few years back there was a similar issue in OpenSSL (and not to knock OpenSSL either!) ...

      1 reply 1 retweet 18 likes
      Show this thread
    2. Colm MacCárthaigh‏ @colmmacc 18 Oct 2018
      • Report Tweet
      • Report NetzDG Violation

      You could send it an out of order "ChangeCipherSuite" message and OpenSSL would skip to the authenticated state for a TLS/SSL connection, bypassing all sorts of important checks. State machines are hard!

      1 reply 2 retweets 25 likes
      Show this thread
    3. Colm MacCárthaigh‏ @colmmacc 18 Oct 2018
      • Report Tweet
      • Report NetzDG Violation

      It's hard to catch these in code reviews because the typical approach is to mix the code that parses messages and the code the proceeds to the next state. For example you might have a parser that handles the first "Hello" message ...

      1 reply 1 retweet 18 likes
      Show this thread
    4. Colm MacCárthaigh‏ @colmmacc 18 Oct 2018
      • Report Tweet
      • Report NetzDG Violation

      before it even runs some piece of code is probably like "hey this is a hello message, call that parser!" and then at the end that parser will have a series of branches that are basically "hey, if I'm in this mode with X enabled, go here next, otherwise go there next".

      1 reply 0 retweets 10 likes
      Show this thread
    5. Colm MacCárthaigh‏ @colmmacc 18 Oct 2018
      • Report Tweet
      • Report NetzDG Violation

      When you're reading the code locally everything makes sense, because you're not thinking of other entry points or things being out of order. There's nothing glaring there.

      1 reply 1 retweet 12 likes
      Show this thread
    6. Colm MacCárthaigh‏ @colmmacc 18 Oct 2018
      • Report Tweet
      • Report NetzDG Violation

      One way to catch these errors is to use a protocol fuzzer; something that sends messages in random orders, tries to jam things up. But those are hard to write ... the messages need to be somewhat valid to get so far, and the combinatorial space to explore can be HUGE.

      1 reply 0 retweets 28 likes
      Show this thread
    7. Colm MacCárthaigh‏ @colmmacc 18 Oct 2018
      • Report Tweet
      • Report NetzDG Violation

      In s2n we do something differently. We borrow a trick first learned from S3's Doug Lawrence, combined with another trick from @signalapp's @trevp__ .... we linearize the state machine into a static table, and we try to negotiate EVERYTHING just once. O.k. what does that mean ...

      1 reply 7 retweets 54 likes
      Show this thread
    8. Colm MacCárthaigh‏ @colmmacc 18 Oct 2018
      • Report Tweet
      • Report NetzDG Violation

      O.k. so rather than having message parsers and generators that can transition states at all, we make them standalone, all they do is parse or generate messages. So how do we know which ones to call and when?

      1 reply 1 retweet 18 likes
      Show this thread
    9. Colm MacCárthaigh‏ @colmmacc 18 Oct 2018
      • Report Tweet
      • Report NetzDG Violation

      We put everything in a table, and use function pointers, see s2n's at:https://github.com/awslabs/s2n/blob/master/tls/s2n_handshake_io.c#L62 …

      2 replies 0 retweets 39 likes
      Show this thread
    10. Jiliac‏ @Jilyac 21 Oct 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @colmmacc

      So if I understand this correctly, this means you enumerate all possible states and all possible messages,. And that makes it easier to test because you can just go over them one by one. Is my understanding correct?

      1 reply 0 retweets 0 likes
      Colm MacCárthaigh‏ @colmmacc 21 Oct 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Jilyac

      We enumerate of every valid order of states. Then, by choosing an enumeration just once, we reduce every state transition to a simple one step forward.

      6:00 PM - 21 Oct 2018 from Seattle, WA
      1 reply 0 retweets 0 likes
        1. New conversation
        2. Jiliac‏ @Jilyac 21 Oct 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @colmmacc

          Ah I think I got it. With your code being structured this way, you ensure that there is a single "entry point" to each state and that it comes from a correct previous state?

          1 reply 0 retweets 0 likes
        3. Colm MacCárthaigh‏ @colmmacc 21 Oct 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @Jilyac

          Yep! I think of it like a single entry point into a strong "chain" of states. Rather than each state deciding where to go next ... which has been more likely to go wrong.

          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