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 Apr 24
      • Report Tweet
      • Report NetzDG Violation

      The updated Apple | Google COVID-19 exposure notification cryptography paper is here: https://covid19-static.cdn-apple.com/applications/covid19/current/static/contact-tracing/pdf/ExposureNotification-CryptographySpecificationv1.1.pdf … . Going to follow up with observations as I read it.

      1 reply 28 retweets 65 likes
      Show this thread
    2. Colm MacCárthaigh‏ @colmmacc Apr 24
      • Report Tweet
      • Report NetzDG Violation

      O.k. so first off; I've seen speculation that the change from HMAC to AES is to save power. I don't think this is true. The change to AES is to allow the phone to broadcast some encrypted data (the bluetooth power level) that can later be decrypted.

      1 reply 0 retweets 4 likes
      Show this thread
    3. Colm MacCárthaigh‏ @colmmacc Apr 24
      • Report Tweet
      • Report NetzDG Violation

      The power theory is silly IMO; Bluetooth IDs are only generated 144 times a day, the battery savings would be negligible.

      1 reply 0 retweets 5 likes
      Show this thread
    4. Colm MacCárthaigh‏ @colmmacc Apr 24
      • Report Tweet
      • Report NetzDG Violation

      Broadcasting the transmit power level of the bluetooth assists the app in assessing distance. The receiving phone stores the observed signal strength on its end, and later when everything can be decrypted, it allows the system to est. the distance between the sender and receiver.

      1 reply 0 retweets 4 likes
      Show this thread
    5. Colm MacCárthaigh‏ @colmmacc Apr 24
      • Report Tweet
      • Report NetzDG Violation

      Anyway, let's get into some cryptography details! Basically every time the bluetooth MAC changes, the device produces a new identifier which an AES ECB (!!) encrypted version of the current time-internal number. Don't panic: ECB is ok here, time-intervals won't repeat.

      1 reply 0 retweets 4 likes
      Show this thread
    6. Colm MacCárthaigh‏ @colmmacc Apr 24
      • Report Tweet
      • Report NetzDG Violation

      That 16-byte encrypted blob is broadcast on the wire, but it also the IV for an AES-CTR encrypted 4 byte section of metadata. What's in the metadata? Here's the list from the Bluetooth spec.pic.twitter.com/HWGhfcc6ou

      1 reply 0 retweets 3 likes
      Show this thread
    7. Colm MacCárthaigh‏ @colmmacc Apr 24
      • Report Tweet
      • Report NetzDG Violation

      On the surface of it, this doesn't look safe. If the power level changes, then byte 1 will change, but get encrypted using the same key, IV pair, and broadcast. This leaks one byte of ciphertext. Since there's no MAC of any kind, it also means these values can be forged.

      1 reply 0 retweets 2 likes
      Show this thread
    8. Colm MacCárthaigh‏ @colmmacc Apr 24
      • Report Tweet
      • Report NetzDG Violation

      Like I could grab your broadcast bluetooth ID, change that byte, and rebroadcast it .. and it would decrypt and register just fine. Hard to think of a useful attack though. I can't predict the decrypted value, just corrupt it.

      1 reply 0 retweets 2 likes
      Show this thread
    9. Colm MacCárthaigh‏ @colmmacc Apr 24
      • Report Tweet
      • Report NetzDG Violation

      If I re-broadcast all 256 potential values, some would be bound to register as within the "proximity radius of danger", but it'd be an easy attack to detect.

      1 reply 0 retweets 1 like
      Show this thread
      Colm MacCárthaigh‏ @colmmacc Apr 24
      • Report Tweet
      • Report NetzDG Violation

      And Apple | Google are careful not to leak the ciphertext byte. The bluetooth paper makes clear that you have to change the metadata at the same time as the key used to encrypt it (which is valid for a time interval).pic.twitter.com/nen8STOZx0

      1:34 PM - 24 Apr 2020
      • 1 Like
      • the (distant) Dude (at a distance)
      1 reply 0 retweets 1 like
        1. New conversation
        2. Colm MacCárthaigh‏ @colmmacc Apr 24
          • Report Tweet
          • Report NetzDG Violation

          On the whole, it looks ok to me if a bit precarious. If the Bluetooth MAC address changes and the key-rotations get out of phase, things go bad. If the app re-generates an ID when the power level changes, that's worse, though not the end of the world.

          1 reply 0 retweets 2 likes
          Show this thread
        3. Colm MacCárthaigh‏ @colmmacc Apr 24
          • Report Tweet
          • Report NetzDG Violation

          This all reads like a well-integrated effort by professionals working across cryptographic, radio, and epidemiological boundaries to make smart trade-offs.

          1 reply 1 retweet 8 likes
          Show this thread
        4. Colm MacCárthaigh‏ @colmmacc Apr 24
          • Report Tweet
          • Report NetzDG Violation

          Addendum: maybe the power theory isn't so silly. I forgot that the app also has to re-generate the IDs of every infected person to determine matches. AES will save a lot of power in that case.

          0 replies 1 retweet 4 likes
          Show this thread
        5. 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