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. hanno‏ @hanno 20 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @wdormann @Scott_Helme

      there's no clear guideline on this. there's a BR rule saying that CAs should prevent the use of known compromised keys, and the debian openssl bug is always the prime example, but there's no standard practice which keys should be blacklisted.

      1 reply 0 retweets 2 likes
    2. hanno‏ @hanno 20 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @hanno @wdormann @Scott_Helme

      I had all kinds of weird experiences, including I reported a key compromise, cert got revoked, new cert got created with the same key (at the same CA). I also found debian weak keys last year in active certs, aka 10 years later.

      1 reply 0 retweets 4 likes
    3. hanno‏ @hanno 20 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @hanno @wdormann @Scott_Helme

      of course you cannot possibly expect that a CA knows about all private keys available anywhere on the internet. it would be an idea to have a shared database of compromised keys (there's things like https://github.com/BenBE/kompromat  where such keys are collected)

      1 reply 0 retweets 2 likes
    4. Will Dormann‏ @wdormann 20 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @hanno @Scott_Helme

      I figured as much. Since it's not really any secret, the following two keys have been used to obtain certificates by CAs (@GoDaddy, @globalsign, @digicert): https://github.com/nodejs/node/blob/master/deps/npm/node_modules/node-gyp/test/fixtures/server.key …https://github.com/gruntjs/grunt-contrib-connect/blob/master/tasks/certs/server.key …

      1 reply 0 retweets 0 likes
    5. hanno‏ @hanno 20 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @wdormann @Scott_Helme and

      two? I only see one.

      1 reply 0 retweets 0 likes
    6. Will Dormann‏ @wdormann 20 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @hanno @Scott_Helme and

      Ah, it looks like Twitter leaves the first link as a hyperlink, and the second one is made "prettier". The first is a nodejs link, the second is a gruntjs link.

      1 reply 0 retweets 0 likes
    7. BenBE‏ @BenBE1987 20 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @wdormann @hanno and

      Thx, added to my kompromat repository. As nodejs contained several more keys it might take a bit, until I push the changes. P.S.: When you're done with notifying affected users of the initially mentioned key collection I'd be happy about a PR to add them too.

      1 reply 0 retweets 2 likes
    8. hanno‏ @hanno 20 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @BenBE1987 @wdormann and

      I checked all the nodejs keys, several of them are the same in different files, better filter out the duplicates.

      1 reply 0 retweets 0 likes
    9. BenBE‏ @BenBE1987 20 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @hanno @wdormann and

      At least about 200 are within https://github.com/nodejs/node/blob/8c9aaacb333a0223243eda9b3551dbf26fdb260a/deps/openssl/openssl/test/recipes/30-test_evp_data/evppkey_ecc.txt … … Still at collecting and filtering them …

      1 reply 0 retweets 0 likes
    10. hanno‏ @hanno 20 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @BenBE1987 @wdormann and

      that looks like a bundled copy of openssl

      1 reply 0 retweets 0 likes
      Will Dormann‏ @wdormann 21 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @hanno @BenBE1987 and

      As I look at my pile of CAs to contact, it's looking like I might need help with the best way to get through to each of them. Picking one off the top of the list as an example, how would one start with https://crt.sh/?caid=1663  and end up with an email address to notify?

      1:38 PM - 21 Mar 2019
      • 1 Retweet
      • 1 Like
      • BenBE
      1 reply 1 retweet 1 like
        1. BenBE‏ @BenBE1987 21 Mar 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @wdormann @hanno and

          You might be able to look it up via the CCADB (cf. https://ccadb.org/resources ). On https://ccadb-public.secure.force.com/mozilla/AllCAAIdentifiersReport … you find Sectigo to be responsible for the DOMENY. This gives us https://www.comodo.com/repository/Comodo_CA_CPS_4.1.8.pdf … as the CP (cf. links on CCADB page). Try to contact them and let them escalate. HTH.

          0 replies 1 retweet 1 like
          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