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
marcan42's profile
Hector Martin
Hector Martin
Hector Martin
@marcan42

Tweets

Hector Martin

@marcan42

If it ain't broke, I'll fix it! I'm porting Linux to Apple Silicon Macs at @AsahiLinux. http://patreon.com/marcan  | http://github.com/sponsors/marcan 

Tokyo, Japan
marcan.st
Joined May 2009

Tweets

  • © 2021 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. Hector Martin‏ @marcan42 23 Feb 2017
      • Report Tweet
      • Report NetzDG Violation

      Finally a SHA-1 collision. TL;DR: same-prefix collision, don't panic *yet*, but Git better start thinking of SHA-256 and don't trust PDFs.

      4 replies 55 retweets 44 likes
    2. Hector Martin‏ @marcan42 23 Feb 2017
      • Report Tweet
      • Report NetzDG Violation
      Replying to @marcan42

      Remember, this SHA1 attack is *not* the attack that broke MD5 TLS certs and gave us Flame. *This* attack on MD5 you can run on a smartphone.

      2 replies 10 retweets 10 likes
    3. Hector Martin‏ @marcan42 23 Feb 2017
      • Report Tweet
      • Report NetzDG Violation
      Replying to @marcan42

      This SHA1 attack does NOT allow you to collide an innocent-looking file with a malicious file. You need TWO blatantly malicious files.

      2 replies 13 retweets 10 likes
    4. Hector Martin‏ @marcan42 23 Feb 2017
      • Report Tweet
      • Report NetzDG Violation
      Replying to @marcan42

      ... of course, if nobody's looking at the hex dump, one of those files might not look malicious when you open it. Hence the PDF trick.

      1 reply 3 retweets 5 likes
    5. Hector Martin‏ @marcan42 23 Feb 2017
      • Report Tweet
      • Report NetzDG Violation
      Replying to @marcan42

      Similarly, you could make two colliding binaries and have them behave differently, but the "evil" code would have to exist in both.

      1 reply 6 retweets 8 likes
    6. Hector Martin‏ @marcan42 23 Feb 2017
      • Report Tweet
      • Report NetzDG Violation
      Replying to @marcan42

      This is the last nail in the "but it isn't broken yet" excuse to keep using SHA-1, so if you haven't *started* migrating yet, start *now*.

      1 reply 12 retweets 18 likes
    7. Hector Martin‏ @marcan42 23 Feb 2017
      • Report Tweet
      • Report NetzDG Violation
      Replying to @marcan42

      Hash attacks 101: preimage=any clean file; chosen prefix=64b of junk in otherwise clean known file; same prefix=both files evil.

      1 reply 5 retweets 7 likes
      Hector Martin‏ @marcan42 23 Feb 2017
      • Report Tweet
      • Report NetzDG Violation

      preimage=we're screwed (not even MD*2* is preimage-broken); chosen prefix=Flame, git totally broken; same prefix=git safe-ish for code.

      7:08 AM - 23 Feb 2017
      • 6 Retweets
      • 12 Likes
      • Kyle Howells Alexey Kulaev KHRoN Ramon Echavarri RAED ALGHAMDI http 🏝 Taudry Hepburn 🏝 ‏pix Manuel Urueña
      2 replies 6 retweets 12 likes
        1. New conversation
        1. Hector Martin‏ @marcan42 23 Feb 2017
          • Report Tweet
          • Report NetzDG Violation
          Replying to @marcan42

          If you're putting binary files in Git without carefully vetting their contents, time to start pestering the devs to switch to a better hash.

          2 replies 4 retweets 9 likes
        2. Damian Yerrick‏ @PinoBatch 23 Feb 2017
          • Report Tweet
          • Report NetzDG Violation
          Replying to @marcan42

          PNG is binary (in the sense of not text) but has internal CRC. Are these reasonably safe?

          1 reply 0 retweets 0 likes
        3. Show replies
      2. Show additional replies, including those that may contain offensive content

      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

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