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 @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
    2. 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
    3. 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
    4. 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
    5. 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 replies 0 retweets 13 likes
    6. 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
    7. 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
    8. Jun Kokatsu‏ @shhnjk 11 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @taviso

      If I still get a bounty after making it public, sure!

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

      I checked, they said just comment on the bugs you want opened or ask via usual channels 🙂

      1 reply 0 retweets 1 like
    10. Jun Kokatsu‏ @shhnjk 11 Jun 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @taviso

      Got it. Hope you can now believe that it’s difficult for even Chrome to fix all vulns within 90 days😊

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

      When did I say that all vulnerabilities can be fixed in 90 days? I certainly think that all of those bugs could be fixed in 90 days, but it's a totally rational decision to not fix them and I do think they should be public.

      6:53 PM - 11 Jun 2019
      • 4 Likes
      • Jocelito Nimes no but do you ever feel bad sometimes crankycatcoder
      1 reply 0 retweets 4 likes
        1. New conversation
        2. Jun Kokatsu‏ @shhnjk 11 Jun 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @taviso

          Yes, I agree that if some vulns aren’t being patched for a long time, those should be made public to protect users. But 90 days for all vulns seems difficult. And I believe mandating the deadline makes less important bugs being prioritized over important bugs, and that’s bad🙂

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

          I agree that making it public will protect users. If Microsoft can't find the resources to fix all the vulnerability reports they receive in three months (!), that is very worrying indeed. Do you think users should be more aware that is the case?

          1 reply 2 retweets 11 likes
        4. 4 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