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. Richard Bejtlich‏Verified account @taosecurity 11 Jun 2019
      • Report Tweet
      • Report NetzDG Violation

      Richard Bejtlich Retweeted Tavis Ormandy

      Man, this is petty. The Microsoft of 2019 is not the Microsoft of 1999 or even 2009. You don't need to prompt them with this stunt. MS said they would get the patch delivered in the July update because they wanted improved testing. Microsoft is not the problem in this scenario.https://twitter.com/taviso/status/1138469652571467776 …

      Richard Bejtlich added,

      Tavis OrmandyVerified account @taviso
      Today is day 91, so the issue is now public. I consider this relatively low severity, but you could take down an entire Windows fleet relatively easily, so it's worth being aware of. https://bugs.chromium.org/p/project-zero/issues/detail?id=1804 …
      Show this thread
      16 replies 31 retweets 140 likes
    2. J Stauffer‏ @j_stauffer 11 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @taosecurity

      I’m going to side w/ @taviso on this. 90 days is plenty of time and vendors should be held to the consequences of not responsibly fixing security issues. As consumers, IT/sec pros, etc. we put a lot of trust in these companies. Telling us they need “testing time” is stalling.

      3 replies 0 retweets 5 likes
    3. Orion Edwards‏ @borland 12 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @j_stauffer @taosecurity @taviso

      This affects anything related to windows crypto. If the fix is not trivial and/or has potential side effects, consider *how many* pieces of software on how many machines could be impacted. Oh but some dude from Google with no responsibility thinks that 90 days is plenty. Ok then

      1 reply 1 retweet 6 likes
    4. J Stauffer‏ @j_stauffer 12 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @borland @taosecurity @taviso

      Um...the term “responsible disclosure” comes to mind here. There are researchers that post vulns and POC code without notifying the vendor; putting the world at risk. Responsible researchers give the minimum of 90 days before going public. 3 mons. is plenty of time to fix a vuln

      1 reply 0 retweets 0 likes
    5. This Tweet is unavailable.
    6. Tavis Ormandy‏Verified account @taviso 12 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @dogsbollards @j_stauffer and

      In your opinion, Microsoft are literally incapable of fixing a Windows exploit safely in three months? That's bad news, as Windows zero days are found in the wild quite regularly. Would you say that it's dangerous to use Windows in any mission critical role because of this? 🤔

      2 replies 0 retweets 4 likes
    7. This Tweet is unavailable.
    8. J Stauffer‏ @j_stauffer 12 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @dogsbollards @taviso and

      It’s not our “arbitrary 90 days.” This is the agreed upon term limit responsible vuln researchers use. So what is a reasonable time limit? There’s no money in vuln management, ergo; typically not a priority. All this time they’re “looking into it,” your system is vulnerable.

      1 reply 0 retweets 2 likes
    9. Orion Edwards‏ @borland 12 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @j_stauffer @dogsbollards and

      Microsoft fix bugs in under 90 days all the time, as do other big OS vendors, I’m sure you’ve experienced that before in your position @taviso. Not all bugs are the same though, so to have a policy as black and white as 90 days or GTFO seems bad...

      1 reply 0 retweets 1 like
      Tavis Ormandy‏Verified account @taviso 12 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @taviso @borland and

      This "black and white" argument is absolute nonsense, you can choose any number of days you like to leave your users vulnerable. So long as that number doesn't exceed 90. That is how deadlines work.

      12:43 PM - 12 Jun 2019
      0 replies 0 retweets 0 likes

      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