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.
  • 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
agl__'s profile
Adam Langley
Adam Langley
Adam Langley
@agl__

Tweets

Adam Langley

@agl__

imperialviolet.org
Joined January 2011

Tweets

  • © 2018 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • 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. Deirdre Connolly‏ @durumcrustulum Nov 6
      Replying to @BRIAN_____

      No mention of *ring* I guess :/

      1 reply 0 retweets 1 like
    2. Joshua Liebow-Feeser‏ @joshlf_ Nov 6
      Replying to @durumcrustulum @BRIAN_____

      We've got different design goals. Ring is moving towards a pure-Rust implementation, while we're sticking BoringSSL only. Also, we're working on an introductory blog post which goes into more detail, but Hacker News jumped the gun :)

      3 replies 1 retweet 4 likes
    3. Brian Smith‏ @BRIAN_____ Nov 7
      Replying to @joshlf_ @durumcrustulum

      I'm not sure that distinction will persist long-term. It depends on what kind of non-OpenSSL API boundary BoringCrypto is able/willing to provide, the memory allocation strategies it supports, the latency of the verification of its memory safety & correctness.

      1 reply 0 retweets 1 like
    4. Joshua Liebow-Feeser‏ @joshlf_ Nov 7
      Replying to @BRIAN_____ @durumcrustulum

      They're pretty bound by (loose) API backwards-compatibility, so I don't expect the API to change drastically any time soon. I can't speak to allocation or formal verification; @davidben__ or @agl__ might know more.

      1 reply 0 retweets 1 like
    5. Brian Smith‏ @BRIAN_____ Nov 7
      Replying to @joshlf_ @durumcrustulum and

      It's not so much about changing the existing API as it is about extending it to support a non-OpenSSL API. With *ring* one can do everything, (digests, AEADs, and ECC, etc.) except RSA without heap allocs. In contrast, in OpenSSL they're moving to requiring malloc for everything.

      1 reply 0 retweets 1 like
    6. Joshua Liebow-Feeser‏ @joshlf_ Nov 7
      Replying to @BRIAN_____ @durumcrustulum and

      Oh I see your point. Some of BoringSSL's API is already that way, like the Ed/X25519 stuff. Not sure how far they can push it for the existing APIs, though.

      1 reply 0 retweets 0 likes
    7. David Benjamin‏ @davidben__ Nov 7
      Replying to @joshlf_ @BRIAN_____ and

      I think my current view on mallocs is that they're worth clearing where easy or perf-impacting. Otherwise it probably does not justify maintaining a parallel API on it's own. But if I'm already reworking something, it's on the back of my mind.

      1 reply 0 retweets 2 likes
      Adam Langley‏ @agl__ Nov 7
      Replying to @davidben__ @joshlf_ and

      Also we're not at all suggesting that BoringSSL is some platonic ideal. We need it to support vast amounts of code that grew up with OpenSSL. It's very much shaped to meet those, Google-specific, needs. If you're not Google, the BoringSSL API is unlikely to be best for you.

      10:39 AM - 7 Nov 2018
      • 2 Retweets
      • 5 Likes
      • Joachim Schipper Nimrod Aviram Deirdre Connolly Christian Heimes
      1 reply 2 retweets 5 likes
        1. Brian Smith‏ @BRIAN_____ Nov 7
          Replying to @agl__ @davidben__ and

          It's actually more about practicalities, especially w.r.t. the FIPS 140 validation in commercial settings. Also, a lot of the work I have done in *ring* is to sketch the structure of a formally verified implementation and it's not clear that Rust (or even C) is ultimately needed.

          0 replies 0 retweets 2 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

        • © 2018 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Cookies
        • Ads info