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
EdgeSecurity's profile
Edge Security
Edge Security
Edge Security
@EdgeSecurity

Tweets

Edge Security

@EdgeSecurity

Tweets from @zx2c4. Security Research & Consulting. Support WireGuard development via https://patreon.com/zx2c4  https://wireguard.com/donations/  . Or hire us.

edgesecurity.com
Joined January 2015

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. Edge Security‏ @EdgeSecurity 24 Jan 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @matthew_d_green @tqbf and

      Without introducing signatures? Keeping it DH-only? Good luck. If you've got cryptographic advancements like this, I'm sure @trevp__ and the Noise mailing list would be very interested to hear your suggestions.

      1 reply 0 retweets 0 likes
    2. Matthew Green‏ @matthew_d_green 24 Jan 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @EdgeSecurity @tqbf and

      I’m still not clear why the extra (Paterson) message flow can’t be a few extra bytes in the same message as the first normal record flow.

      1 reply 0 retweets 0 likes
    3. Edge Security‏ @EdgeSecurity 24 Jan 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @matthew_d_green @tqbf and

      Because it'd have to then be in every message, due to drops. Same problem as the original. It'd also hurt the MTU and make the state machine hugely more complicated. An additional mandatory message is not acceptable.

      1 reply 0 retweets 1 like
    4. Matthew Green‏ @matthew_d_green 24 Jan 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @EdgeSecurity @tqbf and

      Wait, but the first transport message is “special” already, right? It includes a timestamp that the other messages don’t include?pic.twitter.com/mAinqjyUiZ

      1 reply 0 retweets 0 likes
    5. Matthew Green‏ @matthew_d_green 24 Jan 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @matthew_d_green @EdgeSecurity and

      I may be misreading this section. But if the first message is special and different from the other messages, how do you survive a drop of that message.

      1 reply 0 retweets 0 likes
    6. Edge Security‏ @EdgeSecurity 24 Jan 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @matthew_d_green @tqbf and

      Yes. The first message (I-->R) and second message (R-->I) are the special ones. Those can't be dropped. But if they do drop, then you just start over at the beginning. There's no complex state machine. No reply after timeout --> start protocol over.

      1 reply 0 retweets 0 likes
    7. Edge Security‏ @EdgeSecurity 24 Jan 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @EdgeSecurity @matthew_d_green and

      Adding a third mandatory message would entirely ruin that and blow up a simple rule into a series of complex state machine rules. Rememer: the complexity of state machines rarely grows just linearly.

      1 reply 0 retweets 0 likes
    8. Matthew Green‏ @matthew_d_green 24 Jan 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @EdgeSecurity @tqbf and

      Is this section referring to the first message after the DH or the first message, period.

      1 reply 0 retweets 0 likes
    9. Edge Security‏ @EdgeSecurity 24 Jan 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @matthew_d_green @tqbf and

      First message period.

      1 reply 0 retweets 0 likes
    10. Matthew Green‏ @matthew_d_green 24 Jan 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @EdgeSecurity @tqbf and

      What is the timestamp encrypted under then?

      1 reply 0 retweets 0 likes
      Edge Security‏ @EdgeSecurity 24 Jan 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @matthew_d_green @tqbf and

      ES, SS. Scroll down to section 5.4.2. Probably all of section 5.4 is worth reading and will answer questions you have about those particulars. There's also the Noise spec which is even more detailed. If it still seems vague, I'm also happy to do full-length emails or Hangouts.

      6:45 AM - 24 Jan 2018
      0 replies 0 retweets 0 likes

      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