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
__agwa's profile
Andrew Ayer
Andrew Ayer
Andrew Ayer
@__agwa

Tweets

Andrew Ayer

@__agwa

Bootstrapped founder of @SSLMate, where I make SSL certificates easier and do #webpki and #CertificateTransparency stuff.

Cambridge, MA + SF Bay Area
agwa.name
Joined November 2011

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. Ryan Sleevi‏ @sleevi_ 11 Sep 2019
      • Report Tweet
      • Report NetzDG Violation

      I’ve shared this with @Scott_Helme directly. The most meaningful improves are systemic: clearer and more consistent rules, automatic checks, improved procedures. You don’t need 4,000 certs for that; 4 works just fine. The other 3,996 must go, but systemic change is what matters.

      2 replies 0 retweets 8 likes
      Show this thread
    2. Scott Helme‏Verified account @Scott_Helme 11 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @sleevi_

      I have to admit, I’m still super confused. I only see 3 possible courses of action. 1) Disclose problematic certs to the responsible CA, which is the course of action I chose. I followed the correct procedure for reporting, allowed them the time they need. Seems reasonable.

      1 reply 0 retweets 1 like
    3. Scott Helme‏Verified account @Scott_Helme 11 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Scott_Helme @sleevi_

      2) Disclose a small number to highlight the issue (like serialNumber 0). Surely the CA would look for other serialNumber 0 certs and still need to revoke them anyway? Same amount of work overall. Same outcome.

      1 reply 0 retweets 0 likes
    4. Scott Helme‏Verified account @Scott_Helme 11 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Scott_Helme @sleevi_

      3) Don’t report the issues I found. Certs don’t get revoked, underlying problem doesn’t get fixed.

      1 reply 0 retweets 0 likes
    5. Scott Helme‏Verified account @Scott_Helme 11 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Scott_Helme @sleevi_

      Given that I ruled out option 3, it only left me with option 1 or 2. Given that option 2 was basically the same as option 1, except I would be leaving the CA to find all the other bad certs on their own, I didn’t see the point in keeping the list from them.

      1 reply 0 retweets 0 likes
    6. Scott Helme‏Verified account @Scott_Helme 11 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Scott_Helme @sleevi_

      No matter what happens, mis-issued certificate with bad data need to be revoked/replaced and the CA needs to improve their process to prevent similar issues in the future. Both of those things have happened or are happening.

      1 reply 0 retweets 0 likes
    7. Ryan Sleevi‏ @sleevi_ 11 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Scott_Helme

      I know you're super confused. That's why it's important to highlight to others to not follow in your footsteps here, because it's not helpful. The emphasis on trying to find all bad certificates, rather than to identify, understand, and remediate the systemic issues is bad.

      1 reply 0 retweets 0 likes
    8. Ryan Sleevi‏ @sleevi_ 11 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @sleevi_ @Scott_Helme

      The correct answer is #2, and that you don't see the distinction is the problem. It's about defining the goal and finding the most effective path to it. The goal should be systemic understanding and improvement, and problem reporting is a way that can support and ensure that.

      1 reply 0 retweets 0 likes
    9. Ryan Sleevi‏ @sleevi_ 11 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @sleevi_ @Scott_Helme

      For example, @GarbageTimeHero found examples of problematic certs from a CA that said they'd fixed it. You only need *one* of those to highlight the systemic flaw is unfixed, and to then make sure the CA has the right understanding and fixes in place before reporting more.

      1 reply 0 retweets 1 like
    10. Ryan Sleevi‏ @sleevi_ 11 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @sleevi_ @Scott_Helme

      The correct answer is #2. It's always #2. Does the CA understand the issue? Do they have a reasonable and reliable fix? Can they discover other issues? You just need a few certs to show the pattern, and a few more to evaluate the fix. If the CA doesn't find the rest, report then

      2 replies 0 retweets 2 likes
      Andrew Ayer‏ @__agwa 11 Sep 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @sleevi_ @Scott_Helme

      e.g. with Certinomis it became clear that their "investigations" were just copy-and-pasting the list of certificates from my reports. Had my reports included every misissued certificate, we wouldn't have learned just how bad Certinomis was at incident response.

      9:12 AM - 11 Sep 2019
      • 4 Likes
      • Anne van Kesteren Nimrod Aviram Ryan Sleevi Royce Williams
      2 replies 0 retweets 4 likes
        1. New conversation
        2. Scott Helme‏Verified account @Scott_Helme 11 Sep 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @__agwa @sleevi_

          That's working on the assumption that my list contained all affected certificates. I'm not making an assertion that all other certs are ok and the CA still needs to look into that. All I'm saying is I found these that are bad.

          1 reply 0 retweets 0 likes
        3. Scott Helme‏Verified account @Scott_Helme 11 Sep 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @Scott_Helme @__agwa @sleevi_

          I'm not sure I'm comfortable with the approach either. Intentionally withholding information from the CA to see if they catch it? When I find problems I give the organisation I'm reporting it to all of the information I have.

          1 reply 0 retweets 0 likes
        4. 13 more replies
        1. New conversation
        2. Royce Williams‏ @TychoTithonus 11 Sep 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @__agwa @sleevi_ @Scott_Helme

          .@winxp5421 had exactly the same experience reporting @Namecheap's silent-in-the-GUI DNSSEC activation failures. They were only fixing reported ones. He learned to only a report a small subset & hold the remaining ones in reserve to verify if they'd fixed the problem system-wide.

          2 replies 0 retweets 1 like
        3. Scott Helme‏Verified account @Scott_Helme 11 Sep 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @TychoTithonus @__agwa and

          But I will still know that with the ongoing monitoring regardless. Seems the only thing we're splitting hairs on here is providing the full list rather than withhold 99% of it and see if they catch it.

          1 reply 0 retweets 0 likes
        4. 3 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