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
pcwalton's profile
Patrick Walton
Patrick Walton
Patrick Walton
@pcwalton

Tweets

Patrick Walton

@pcwalton

Research engineer at Mozilla

San Francisco, CA
pcwalton.github.io
Joined November 2009

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. Matthew Green‏ @matthew_d_green 31 Jul 2019
      • Report Tweet
      • Report NetzDG Violation

      Matthew Green Retweeted Hamid K

      How many of the NSO Group remote exploits are just flavors of “iMessage parsing is a disaster”, I wonder.https://twitter.com/hkashfi/status/1156475870107844608?s=21 …

      Matthew Green added,

      Hamid K @hkashfi
      CVE-2019-8646 (iMessage) is a scary bug! Leaking files remotely, without user interaction, via a callback from iOS. Delivery of SMS database in a silver plate via 0 tap, anyone? https://bugs.chromium.org/p/project-zero/issues/detail?id=1858 … Other 4 bugs are as bad: https://bugs.chromium.org/p/project-zero/issues/list?q=label%3AiMessage&can=1 … you dead if not on iOS 12.4
      5 replies 29 retweets 94 likes
    2. Perry E. Metzger‏ @perrymetzger 31 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @matthew_d_green

      How many remote exploits are generally flavors of "parsing is a disaster"? Most of them, really. This is why LangSec strikes me as such an important idea.

      1 reply 3 retweets 11 likes
    3. Matthew Green‏ @matthew_d_green 31 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @perrymetzger

      It depends how many different things you parse. And in that sense, iMessage is qualitatively and quantitatively a disaster.

      1 reply 0 retweets 4 likes
    4. Dino A. Dai Zovi‏ @dinodaizovi 31 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @matthew_d_green @perrymetzger

      Parsing vulnerabilities are merely the most surface level class of memory corruption. State and sequence-based memory corruption (what some have referred to as “weird machines”) are not affected by LangSec approaches. Memory safety is a more general solution than secure parsing.

      1 reply 2 retweets 14 likes
    5. Dino A. Dai Zovi‏ @dinodaizovi 31 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @dinodaizovi @matthew_d_green @perrymetzger

      For example, if you analyze the CFF exploit in jailbreakme 2.0 (https://www.theiphonewiki.com/wiki/Star ), the corruption is in evaluation of a font program that exceeds assumed font program stack bounds. I’m not sure how LangSec considers issues like this.

      4 replies 1 retweet 1 like
      Patrick Walton‏ @pcwalton 1 Aug 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @dinodaizovi @matthew_d_green @perrymetzger

      If the CFF parser had been implemented in a memory safe language, this wouldn’t have been exploitable as you would get an array bounds check exception.

      3:09 PM - 1 Aug 2019
      1 reply 0 retweets 0 likes
        1. New conversation
        2. Dino A. Dai Zovi‏ @dinodaizovi 1 Aug 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton @matthew_d_green @perrymetzger

          Yes, that’s why I consider memory safety a fix here versus LangSec, which I understand to more oriented around the parsing.

          1 reply 0 retweets 0 likes
        3. Perry E. Metzger‏ @perrymetzger 1 Aug 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @dinodaizovi @pcwalton @matthew_d_green

          You need both if you value both correctness and memory safety.

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