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. hedge.txt | Mostly Inactive, except when not‏ @hedgeberg 17 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @syncsrc

      You're still missing the point. There are a lot of hardware vulns out there, I know the majority are not side channels. I'm only talking about side channels here, see: "whole new attack surface". Theres a lot to be said for vendor flaws but that's not what I'm talking about here.

      1 reply 0 retweets 2 likes
    2. Matt King‏ @syncsrc 17 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @hedgeberg

      Assigning blame here is hard. Si vendors knew about side channels but repeatedly disregarded and downplayed the threat, and underfunded security in general. No one will ever know if Spectre could have been prevented, but the industry didn't even try.

      1 reply 0 retweets 2 likes
    3. Matthew Green‏ @matthew_d_green 17 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @syncsrc @hedgeberg

      In fact, they designed entire new security infrastructure that fundamentally depended on the absence of side channels. With potentially catastrophic consequences if it gets widely adopted and broken.

      2 replies 0 retweets 5 likes
    4. Hector Martin‏ @marcan42 17 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @matthew_d_green @syncsrc @hedgeberg

      SGX aside, nevermind virtualization and the whole cloud craze. Not all side channels are created equal. There's a reason nobody but Intel is vulnerable to L1TF. Nobody in their right mind would think short-circuiting EPT is ever okay, even if you're in speculation.

      1 reply 2 retweets 5 likes
    5. Hector Martin‏ @marcan42 17 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @marcan42 @matthew_d_green and

      I get that the industry wasn't really on the ball on this one, but there's a pretty massive difference between Spectre v1 (a fundamental security issue with speculation that affects the whole industry) and L1TF (Intel what the fuck are you doing?), other bugs being in the middle.

      1 reply 0 retweets 5 likes
    6. Hector Martin‏ @marcan42 17 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @marcan42 @matthew_d_green and

      This sounds like no vendor had a proper security team evaluating these kinds of side channels, but on top of that it seems Intel likely had an explicit policy of "literally anything goes before instructions retire, no matter how insane", which is crazy.

      1 reply 1 retweet 5 likes
    7. hedge.txt | Mostly Inactive, except when not‏ @hedgeberg 17 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @marcan42 @matthew_d_green @syncsrc

      This is exactly the damn point though Marcan, when you're fighting with a million other factors and trying to squeeze out performance that's an easy mistake to make, and an easy one for a red team to overlook. It's not /good/, and it's not ok that its a problem that exists...

      1 reply 0 retweets 1 like
    8. hedge.txt | Mostly Inactive, except when not‏ @hedgeberg 17 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @hedgeberg @marcan42 and

      ...but this entire attitude is incredibly unhelpful. There are no good security verification tools in silicon design beyond manual review. It's easy for us to call out Intel, but we're post-discovery now. How do we make sure this doesn't happen in the future instead?

      2 replies 0 retweets 1 like
    9. hedge.txt | Mostly Inactive, except when not‏ @hedgeberg 17 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @hedgeberg @marcan42 and

      Pretty sure the answer isn't just "fuck Intel" and it's not "down with CISC", this is a lot more nuanced than any of you are taking the time to acknowledge. This was likely the mistake of a single engineer that noone caught, and that's understandable becsuse...

      1 reply 0 retweets 1 like
    10. hedge.txt | Mostly Inactive, except when not‏ @hedgeberg 17 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @hedgeberg @marcan42 and

      ...CPU architecture design students werent taught this stuff until really recently. It's easy for us to call them out, but how are they supposed to know if they weren't taught? Shaming mistakes instead of teaching people how to do better only causes more problems.

      2 replies 0 retweets 0 likes
      Hector Martin‏ @marcan42 17 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @hedgeberg @matthew_d_green @syncsrc

      I'm shaming the *company*, not the *people*. Intel has more than enough money that they should've cared about this stuff, they should've hired people who could point at things like this and say it's a bad idea.

      12:04 PM - 17 Aug 2018
      • 2 Likes
      • meowy catgirl Matt King
      1 reply 0 retweets 2 likes
        1. New conversation
        2. Hector Martin‏ @marcan42 17 Aug 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @marcan42 @hedgeberg and

          The problem isn't the people working for Intel, it's that Intel allowed things to get this ridiculous. And usually when things get this ridiculous *someone* notices, and I bet someone did, and I bet someone in management shut them down.

          1 reply 0 retweets 1 like
        3. hedge.txt | Mostly Inactive, except when not‏ @hedgeberg 17 Aug 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @marcan42 @matthew_d_green @syncsrc

          That's a pretty bold statement to be making considering how little we know about the internal operations, and whether or not you think you're shaming the company, they don't care, the people that do care are the engineers there and everywhere else that read what we say.

          1 reply 0 retweets 0 likes
        4. Show 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

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