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
wdormann's profile
Will Dormann
Will Dormann
Will Dormann
@wdormann

Tweets

Will Dormann

@wdormann

Vulnerability Analyst at the CERT/CC. My thoughts are my own, not my employer's.

Joined August 2012

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. Stephen Checkoway‏ @stevecheckoway 16 Nov 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @matthew_d_green @tqbf @kennwhite

      So we could lobby browser to reject certs with these visibility attributes but it could always be done without signaling. I don’t think there’s any way to prevent an endpoint from exposing everything.

      1 reply 0 retweets 0 likes
    2. Matthew Green‏ @matthew_d_green 16 Nov 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @stevecheckoway @tqbf @kennwhite

      There never was. Never could have been. The IETF had the option of making this an extension where at least both sides would have had to opt into it via a TLS extension. That seemed like a pretty sweet deal to me.

      1 reply 0 retweets 0 likes
    3. Stephen Checkoway‏ @stevecheckoway 16 Nov 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @matthew_d_green @tqbf @kennwhite

      I guess, but that wouldn’t preclude doing exactly this. It just provides another mechanism.

      1 reply 0 retweets 0 likes
    4. Matthew Green‏ @matthew_d_green 16 Nov 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @stevecheckoway @tqbf @kennwhite

      Given that this was always going to happen, the whole point was to encourage the industry to do it in the safest way possible, with strong oversight by the IETF. There wouldn’t be any support behind an alternative like this one if the IETF has done that.

      1 reply 0 retweets 3 likes
    5. This Tweet is unavailable.
    6. Kenn White‏Verified account @kennwhite 16 Nov 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @4Dgifts @matthew_d_green @stevecheckoway

      pic.twitter.com/Qxc6dLdA1T

      1 reply 1 retweet 1 like
    7. Will Dormann‏ @wdormann 16 Nov 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @kennwhite @4Dgifts and

      Ah yes, each time an HTTPS site is visited, click through to a screen where a user looks at a field ("Issued by") that is completely arbitrary and attacker-controlled. Got it. :) Perhaps you were being sarcastic, though, in which case I'll show myself to the door...

      2 replies 0 retweets 0 likes
    8. Kenn White‏Verified account @kennwhite 16 Nov 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @wdormann

      an obligatory blast from the past (I mean who doesn't love the name "superfish"). But no, not suggesting reading dialog boxes en masse. If someone were sufficiently motivated, suppose I could envision a Chrome ext warning when connecting to a site signed by a non-built in root.

      1 reply 0 retweets 1 like
    9. Will Dormann‏ @wdormann 16 Nov 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @kennwhite

      Chrome leverages the OS-level root CA store. What distinguishes a built-in root vs. a user-installed root? And in Windows, the trusted root CA list grows with use of the system as well. For example, a clean Win10 install has a smaller list of trusted root CAs. vs one that's used

      2 replies 0 retweets 1 like
    10. Kenn White‏Verified account @kennwhite 16 Nov 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @wdormann

      ah, right. I get FF & Chrome policies reversed. Ftr, I'm not at all suggesting this is a good idea, but /if/ someone were to do this, maybe a web service periodically updated with published OS cert lists could seed it? But really, just, no.

      1 reply 0 retweets 0 likes
      Will Dormann‏ @wdormann 16 Nov 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @kennwhite

      There was some work put into frameworks where browsers would compare certificates presented to you by websites vs. what other folks were seeing (and compared via fingerprints, as opposed to forgeable human-readable names). https://en.wikipedia.org/wiki/Convergence_(SSL) … Sadly, they've been abandoned.

      10:06 AM - 16 Nov 2018
      • 1 Like
      • Kenn White
      1 reply 0 retweets 1 like
        1. John Moser‏ @structuralecon 17 Nov 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @wdormann @kennwhite

          Why not embed the allowable CAs into the DNS records so your browser can hit up the CA's server and check if the certificate is signed by the CA?

          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