• palordrolap@kbin.social
    link
    fedilink
    arrow-up
    5
    arrow-down
    6
    ·
    5 months ago

    My guess is a “solution” to the age-old problem of needing to store a secret in a file that the user can download, thus making the entire system insecure.

    This “solution” appears to be either that the string itself is so outrageous that the user would not believe that it’s the real secret when it is in fact the real secret, leveraging security through obscurity, or else it’s there in place of the real secret that cannot be revealed under pain of death firing, and therefore is accidentally being used instead of that intended secret… so it’s not secret after all.

    Unless they’re doing something incredibly clever to substitute that secret string for the real thing when the time is right and doing it in such a way that the user can’t intercept, someone’s getting fired.

    • dev_null@lemmy.ml
      link
      fedilink
      arrow-up
      5
      ·
      5 months ago

      No, it’s not. It’s part of React internals that you shouldn’t use because your app will break. It’s a warning for developers using React. It’s not a secret of any kind.