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. Ivan Ristic‏ @ivanristic 24 Aug 2019
      • Report Tweet
      • Report NetzDG Violation

      Ivan Ristic Retweeted Cryptoki

      “Support for Short-Term, Automatically-Renewed (STAR) Certificates in ACME”.https://twitter.com/Cryptoki/status/1165299507304816642 …

      Ivan Ristic added,

      Cryptoki @Cryptoki
      lol, so when#cabf Sleevigoogle gets 13 month #tls certs, how long til (cough cough) he comes back for ... 24 hour certs 😆 https://datatracker.ietf.org/doc/draft-ietf-acme-star/ …
      1 reply 4 retweets 14 likes
    2. Ryan Hurst‏Verified account @rmhrisk 24 Aug 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @ivanristic

      I honestly don’t get why this is needed. Keys are cheap, and new keys are desirable, why go out if your way to enable re-use? CAS can re use validation information as well, why complicate the protocol to enable short cutting a few requests?

      2 replies 0 retweets 0 likes
    3. Andrew Ayer‏ @__agwa 24 Aug 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @rmhrisk @ivanristic

      An argument that operators use against short-lived certs is that empirically automated cert issuance has more downtime than OCSP. STAR allows issuance to work like OCSP - new certs distributed via a highly-available CDN and retrieved with unauthenticated GET.

      3 replies 0 retweets 0 likes
    4. Andrew Ayer‏ @__agwa 24 Aug 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @__agwa @rmhrisk @ivanristic

      Key rotation is important, so STAR orders expire, after which the client can renew with a new key. So keys need not be any longer-lived under STAR than they are with today's long-lived certs.

      2 replies 0 retweets 0 likes
    5. Andrew Ayer‏ @__agwa 24 Aug 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @__agwa @rmhrisk @ivanristic

      It may not be necessary for Google, but if this makes short-lived certs palatable to other operators, it's an improvement over the status quo, even if keys are not rotated ~daily.

      2 replies 0 retweets 0 likes
    6. Ryan Hurst‏Verified account @rmhrisk 24 Aug 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @__agwa @ivanristic

      I’m not speaking as Google just Ryan; I get that it lets you renew against same key for a fixed period. That’s the most impactful element of the proposal since cached validations reduce need to recalibrate on renewal. I just ask why?

      1 reply 0 retweets 0 likes
    7. Andrew Ayer‏ @__agwa 24 Aug 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @rmhrisk @ivanristic

      Arguments like https://github.com/WICG/webpackage/issues/378#issuecomment-457011076 …: "7-day lifetime would limit uptime. In practice they see longer downtime periods for certificate issuance than OCSP."

      1 reply 0 retweets 1 like
    8. Ryan Hurst‏Verified account @rmhrisk 24 Aug 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @__agwa @ivanristic

      In practice the reason they see that is they have been using legacy CAs that frequently experience hours of issuance outage. Making the issuance asynchronous doesn’t meaningfully change that a CA outage means you don’t get your new cert.

      1 reply 0 retweets 2 likes
      Andrew Ayer‏ @__agwa 24 Aug 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @rmhrisk @ivanristic

      It seems like batch signing certs and pushing them out to CDNs will always be fundamentally more reliable than an Internet-facing signing-on-demand service, which can be affected by unexpected usage spikes, DoS attacks, buggy clients causing retry storms, etc.

      11:15 AM - 24 Aug 2019
      • 2 Likes
      • Vincent Ryan Hurst
      1 reply 0 retweets 2 likes
        1. New conversation
        2. Ryan Hurst‏Verified account @rmhrisk 24 Aug 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @__agwa @ivanristic

          It’s a bit like rearranging deck chairs on a sinking ship. If your a SAAS service, let’s say WordPress, where you need to spin up a new site for your customer who just completed a wizard, if your cert issuance is down your site is down.

          1 reply 0 retweets 1 like
        3. Ryan Hurst‏Verified account @rmhrisk 24 Aug 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @rmhrisk @__agwa @ivanristic

          Now with the batches signed certs you could have certs on a CDN that were pre produced for your existing customers so they don’t go down also.

          1 reply 0 retweets 1 like
        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