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
jedisct1's profile
Frank
Frank
Frank
@jedisct1

Tweets

Frank

@jedisct1

France
Joined November 2008

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. Robᵉʳᵗ Graham 😷‏ @ErrataRob 21 Mar 2019
      • Report Tweet
      • Report NetzDG Violation

      It's important to note in this "Facebook plain-text password" story that the passwords are being stored with salted scrypt hashes, that's not the issue. Instead, the issue is inadvertent logging of web requests -- which happen to contain clear-text passwords.

      17 replies 265 retweets 568 likes
      Show this thread
    2. Frank‏ @jedisct1 21 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @ErrataRob

      Servers should not see cleartext passwords ever. This is a ticking bomb. https://00f.net/2018/10/18/on-user-authentication/ … https://github.com/jedisct1/fastly-terrarium-examples/tree/master/access_control_example …

      2 replies 6 retweets 43 likes
    3. signal eleven‏ @widdr 21 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @jedisct1 @ErrataRob

      After reading over this (and the docs correction I posted, thanks for the quick fix), I'm curious: What's the driving motivation behind adding the complexity and extra round trip of OPRF salt construction just to involve the server in the construction of the client's secret key?

      2 replies 0 retweets 1 like
    4. signal eleven‏ @widdr 21 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @widdr @jedisct1 @ErrataRob

      I'm not sure I can see what attacks would be viable against a model where we skip this step and simply construct our secret key from a key-stretched (domain || username || password) that are mitigated by the addition of this step.

      2 replies 0 retweets 0 likes
    5. Frank‏ @jedisct1 21 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @widdr @ErrataRob

      `(domain||username||password)` is fine if you don’t care about targeted attacks. As an alternative, a new `(pk, seed)` can be sent by the client after logging in. So that these are constantly changing. By the time a database gets leaked, it’s already obsolete and useless.

      1 reply 0 retweets 0 likes
    6. Frank‏ @jedisct1 21 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @jedisct1 @widdr @ErrataRob

      https://github.com/jedisct1/fastly-terrarium-examples/tree/605500c2828e2dc0a7a0558db4f6da59094e08c7/access_control_example … That was the initial design and implementation of this protocol. But high-profile users that never log in remain vulnerable.

      1 reply 0 retweets 0 likes
    7. signal eleven‏ @widdr 21 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @jedisct1 @ErrataRob

      I always envisioned a plain extension of the usual method: store the pk as the password serverside, bcrypted as normal. Require that it be provided like a password. Generate sk/pk with a keystretcher clientside, plus require the client to sign a server-provided random nonce.

      4 replies 0 retweets 0 likes
      Frank‏ @jedisct1 21 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @widdr @ErrataRob

      Same issue. No salt -> vulnerable to targeted attacks. Stretching server-side -> DoS vector.

      6:32 PM - 21 Mar 2019 from Paris, Ile-de-France
      1 reply 0 retweets 0 likes
        1. New conversation
        2. signal eleven‏ @widdr 21 Mar 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @jedisct1 @ErrataRob

          I have not often seen the static server secret in practice (aka 'salt & pepper'); I would LOVE to see a case study of the efficacy of this practice. Common method today seems to be serverside stretching only, with rate-limiting to solve DoS -- albeit with plaintext passwords 🤢

          1 reply 0 retweets 0 likes
        3. signal eleven‏ @widdr 21 Mar 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @widdr @jedisct1 @ErrataRob

          i get it though: at the cost of an extra round trip and some added complexity, we can 1) mix in a static secret; 2) avoid key stretching serverside; and 3) avoid unnecessary pk retransmission. Pretty neat!

          0 replies 0 retweets 0 likes
        4. End of conversation

      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