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 14 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @tqbf @CiPHPerCoder

      Again: we're obviously on the same page for the unauth'd issue. We differ here because I think the status api is effectively an internal low-level api, and it is unreasonable to hold that to the same bar as a documented and supported high-level api.

      1 reply 0 retweets 1 like
    2. Tavis Ormandy‏Verified account @taviso 14 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @taviso @tqbf @CiPHPerCoder

      Tavis Ormandy Retweeted Tavis Ormandy

      See this tweet.https://twitter.com/taviso/status/996136722546081793 …

      Tavis Ormandy added,

      Tavis OrmandyVerified account @taviso
      Replying to @taviso @tqbf
      Gpgme has user docs, whereas the status api has some org mode README in the source distribution. I'm not convinced it's fair to say "it's a vuln if it's hard to use the low-level internal apis", is there any library that can't be misused if you access private/internal apis? 2/2
      1 reply 0 retweets 0 likes
    3. Thomas H. Ptacek‏ @tqbf 14 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @taviso @CiPHPerCoder

      We may be in distinction-without-a-difference land here. If you’re arguing that nothing in the GPG stack should be using the interfaces they’re using, I don’t have a strong POV on that. Sorry if I’m being obstinate.

      1 reply 0 retweets 2 likes
    4. Tavis Ormandy‏Verified account @taviso 14 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @tqbf @CiPHPerCoder

      Yes, I'm saying clients should be using gpgme, it wraps all of this internal crazy stuff in a high-level, documented and supported api. If clients use the internal stuff directly anyway and then screw it up, I'm saying I don't see how that's a gpg vulnerability.

      2 replies 2 retweets 9 likes
    5. Thomas H. Ptacek‏ @tqbf 14 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @taviso @CiPHPerCoder

      The GPG project itself is vouching for the interface we’re talking about, which is why it’s an issue.

      2 replies 0 retweets 1 like
    6. Tavis Ormandy‏Verified account @taviso 14 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @tqbf @CiPHPerCoder

      I don't speak for them, but I think they vouch for it in the same way that openssl vouches for the bn library: they use it and rely on it. They're pretty upfront that status api is complex and clients should use gpgme, read this blurb: https://www.gnupg.org/software/gpgme/index.html …

      1 reply 0 retweets 1 like
    7. Thomas H. Ptacek‏ @tqbf 14 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @taviso @CiPHPerCoder

      I’m reading message after message talking about exit codes and warnings, and that’s what I have a problem with.

      1 reply 0 retweets 1 like
    8. Harley Watson  🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺‏ @_unlobito 14 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @tqbf @taviso @CiPHPerCoder

      If I understanding correctly, I think @tqbf’s argument is OpenPGP should require you to pass a `--danger-ignore-authentication` errors flag before decrypting at all. Doing so explicitly forces the user to downgrade to a vulnerable state, so naive implementations aren’t hurt.

      3 replies 1 retweet 1 like
    9. Tavis Ormandy‏Verified account @taviso 14 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @_unlobito @tqbf @CiPHPerCoder

      Yes, but this is a low-level api that *has* to expose a lot of legacy design decisions. Naive implementations should use the high-level api, and complaints about confusing api's there are valid - here you're just saying "this complex undocumented thing is complicated".

      1 reply 0 retweets 1 like
    10. Scott Arciszewski‏ @CiPHPerCoder 14 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @taviso @_unlobito @tqbf

      If it's true that it *has* to expose legacy design decisions, then we're better off replacing it rather than trying to fix it.

      1 reply 0 retweets 0 likes
      Tavis Ormandy‏Verified account @taviso 14 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @CiPHPerCoder @_unlobito @tqbf

      I think you missed the point.

      9:17 PM - 14 May 2018
      • 1 Like
      • Marcin Piosek
      1 reply 0 retweets 1 like
        1. rugk‏ @rugkme 14 May 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @taviso @CiPHPerCoder and

          now question: do clients actually use gpgme? And of there is a safe api, gpg should not expose an insecure api at all. When it's exposed, you have to consider clients using it. At least the whole api could be marked depreciated or so and always empty a depreciation warning or so

          0 replies 0 retweets 0 likes
          Thanks. Twitter will use this to make your timeline better. Undo
          Undo

      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