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
taviso's profile
Tavis Ormandy
Tavis Ormandy
Tavis Ormandy
Verified account
@taviso

Tweets

Tavis OrmandyVerified account

@taviso

Vulnerability researcher at Google. This is a personal stream, opinions expressed are mine.

California
taviso.decsystem.org
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. Tavis Ormandy‏Verified account @taviso 11 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @gaztunnock

      The deadline was exceeded.

      2 replies 0 retweets 42 likes
    2. Gareth Tunnock‏ @gaztunnock 11 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @taviso

      if MS had committed to fix it in 120 days, would it still have been de-destricted now?

      1 reply 0 retweets 1 like
    3. Tavis Ormandy‏Verified account @taviso 11 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @gaztunnock

      Yes, that's how deadlines work.

      1 reply 1 retweet 86 likes
    4. Gareth Tunnock‏ @gaztunnock 11 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @taviso

      But you're working with vendors to make the Internet safer for all, so if the vendor, who has to do the work to fix it, says a deadline of 120 days, why not respect that, I honestly don't understand the inflexibility, certainly when dealing with this particular vendor

      3 replies 0 retweets 14 likes
    5. Tavis Ormandy‏Verified account @taviso 11 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @gaztunnock

      The policy is *highly* flexible, any number of days between 0 and 90 is acceptable. In addition, if an update or patch was already scheduled within 14 days of the deadline, we offer a "grace period" to align the schedule.

      4 replies 1 retweet 39 likes
    6. Jun Kokatsu‏ @shhnjk 11 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @taviso

      So in your opinion (or is it Google’s opinion?), all vulnerabilities (from low to critical) should be fixed within 90 days?

      3 replies 0 retweets 8 likes
    7. Tavis Ormandy‏Verified account @taviso 11 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @shhnjk

      Three months is way too high in my opinion, it's a compromise. In open source, the norm is closer to 90 hours. Linus famously tells people not to tell him about bugs if you want them kept secret for more than two weeks, because he'll just fix them.

      2 replies 5 retweets 63 likes
    8. Jun Kokatsu‏ @shhnjk 11 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @taviso

      But even well funded open source software like Chrome still has a dozen of vulns unfixed for a year (and this is just my bugs). I’m hoping that you’ll convince Chrome to fix my bugs within 90 hours so that I can get bounties within a week :D

      1 reply 4 retweets 17 likes
    9. Tavis Ormandy‏Verified account @taviso 11 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @shhnjk

      I don't really have any opinion on bounties sorry, my first thought is that the bounty operator can dictate any terms they like and you have the right to not participate? Happy to hear the counter-argument.

      2 replies 0 retweets 5 likes
    10. Jun Kokatsu‏ @shhnjk 11 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @taviso

      Oh, bounty part was just a humor😊 My point was, even Chrome can’t do 90 days deadlines for all vulnerabilities.

      1 reply 0 retweets 2 likes
      Tavis Ormandy‏Verified account @taviso 11 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @shhnjk

      I think Chrome has a pretty stellar track record on this, and can totally manage 90 days. Give me the bug number and I'll take a look, it's hard for me to believe they're sitting on a 0day for over a year.

      4:33 PM - 11 Jun 2019
      • 13 Likes
      • Jocelito Nimes Elgon View sn0⇂ɹɐW mark risher missoum1307 Roach_Sanderson free chelsea fuck blizzard Liberate Hong Kong
      4 replies 0 retweets 13 likes
        1. New conversation
        2. Jun Kokatsu‏ @shhnjk 11 Jun 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @taviso

          Following are vulns (per Chrome team) that's unfixed for more than a year (oldest one is reported on 2015 😱) 538562 771596 772759 794382 799041 802007 821625 821626 821628 821630 821632 821634 823241 823737 830101 830808 831731 831761 847848

          1 reply 0 retweets 20 likes
        3. Tavis Ormandy‏Verified account @taviso 11 Jun 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @shhnjk

          I clicked through a few, they mostly don't seem like they need to be private to me. I can ping some Chrome developers and say you want them public if you like, it seems fine to me... I would have just made these public. 🤷‍♂️

          2 replies 0 retweets 2 likes
        4. 10 more replies
        1. Eric Lawrence  🎻‏ @ericlaw 11 Jun 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @taviso @shhnjk

          The spectrum of "vulnerabilities" is broader than RCE. And nowadays we are all on the same team. :)

          0 replies 1 retweet 5 likes
          Thanks. Twitter will use this to make your timeline better. Undo
          Undo
        1. Andrew R. Whalley‏ @arw 11 Jun 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @taviso @shhnjk

          Likewise!

          0 replies 0 retweets 3 likes
          Thanks. Twitter will use this to make your timeline better. Undo
          Undo
        1. New conversation
        2. mik‏ @mik235 11 Jun 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @taviso @shhnjk

          Spectre/Meltdown was a little longer IIRC, and they had a few years head start on the mitigation...

          1 reply 0 retweets 0 likes
        3. mik‏ @mik235 11 Jun 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @mik235 @taviso @shhnjk

          (Obviously that was a P0 bug, and everyone including Microsoft got longer to work on it)

          0 replies 0 retweets 0 likes
        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