This thread is frustrating. Everyone seems more interested in nitpicking the specifics of what OP is saying and are ignoring that a forum sends you your password (not an automatically generated one) in an email on registration.

  • mosiacmango@lemm.ee
    link
    fedilink
    arrow-up
    94
    arrow-down
    3
    ·
    3 years ago

    Larian stated on their forum they fixed this behavior and shifted to https 3 years ago. When this was linked several times in thread, people asked OP when this screenshot occured, and OP ignored the questions. Pretty clear that this is a very old screenshot of what is now a non issue.

    What’s to discuss besides OP trying to stir up drama about issues that were resolved years ago?

    • Pyro@lemmy.world
      link
      fedilink
      English
      arrow-up
      18
      ·
      3 years ago

      this is a very old screenshot

      What do you mean? It says “0 minutes ago”! Clearly it’s very recent! /s

    • ono@lemmy.ca
      link
      fedilink
      English
      arrow-up
      12
      arrow-down
      3
      ·
      edit-2
      3 years ago

      FWIW, it’s not fixed. The screen shot may very well be recent.

      (The post in question was still bad reporting, though, for the reasons I detailed in my other comment here.)

      • El Barto@lemmy.worlddeleted by creator
        link
        fedilink
        arrow-up
        6
        ·
        edit-2
        3 years ago

        Are you saying that the parent poster is giving incorrect information?

        Edit: Oy, straight from their membership administration docs (emphasis mine):

        Additionally, using the buttons below, you can delete the user, email the user’s password to him/her, (etc)

        • ono@lemmy.ca
          link
          fedilink
          English
          arrow-up
          6
          ·
          edit-2
          3 years ago

          Are you saying that the parent poster is giving incorrect information?

          Yes. mosiacmango’s comment repeated what others had already said (right down to specific words that I used in the original thread and here), and then jumped to this conclusion:

          Pretty clear that this is a very old screenshot of what is now a non issue.

          Everything about that statement is false. While the circumstances made it seem likely that the screenshot was old, it was not clearly so, and in fact, it turns out the issue is still present. I checked it. A registration email from the test I ran yesterday looked just like the screenshot in question, cleartext password and all.

          Given that Larian reported the issue fixed three years ago, it’s possible that they fixed it locally and some time later upgraded to a new version of the forum software, thereby overwriting the local fix. Perhaps mosiacmango should have considered that before posting incorrect speculation as if it were fact.

        • ____@infosec.pub
          link
          fedilink
          arrow-up
          4
          ·
          3 years ago

          Ouch… This should never be possible, in any world. If the password can be emailed, it can be seen. If it can be seen, it can be stolen.

    • abbadon420@lemm.ee
      link
      fedilink
      arrow-up
      1
      arrow-down
      12
      ·
      3 years ago

      It’s still an interesting case to discuss and learn about. We don’t ignore and forget about ww2, just because it’s over, do we?!

  • ono@lemmy.ca
    link
    fedilink
    English
    arrow-up
    52
    arrow-down
    1
    ·
    3 years ago

    I think the OP of that post would have had a better reception if they had:

    • Responsibly disclosed what they found, rather than using it to stir up drama on social media.
    • Mentioned that it’s just a web forum account, not connected to game accounts or anything else of value.
    • Targeted the software vendor (https://www.ubbcentral.com/) instead of picking on one particular customer who used that software.
    • Refrained from spreading misconceptions and unfounded assumptions about how the technology works.
    • Responded to the reasonable follow-up questions, such as those that came when readers discovered that the problem was reported fixed three years ago.

    People in that thread responded with skepticism and criticism to an irresponsible, misdirected, misleading, alarmist mess of a post. That’s hardly surprising.

  • Aa!@lemmy.world
    link
    fedilink
    arrow-up
    43
    arrow-down
    2
    ·
    3 years ago

    This was hashed out pretty thoroughly in that thread.

    The initial concern over the password being stored in plaintext was shown to be a mistaken assumption, and it was made clear that this kind of email doesn’t happen anymore, it’s an outdated problem.

    No need to keep the discussion going past that, is there? Much less spread it around?

    • adhdplantdev@lemm.ee
      link
      fedilink
      arrow-up
      10
      arrow-down
      4
      ·
      3 years ago

      Sending passwords via email Will compromise any passwords sent via email. Regardless if the password is stored anywhere in the process if the password is sent via email it is compromised and no longer safe to use. Email is not end and encrypted you have no idea who’s running the mail exchange servers that your email follows, it’s entirely possible for this company to store that password in a log dealing with their email servers. Password sent via email should be considered immediately compromised and any sites following a practice like this should not be trusted with standard passwords which you shouldn’t be using anyway.

      • Aa!@lemmy.world
        link
        fedilink
        English
        arrow-up
        17
        ·
        3 years ago

        Right, and everyone agreed that wasn’t the greatest practice. Two years ago.

        This thread from two days ago was bringing attention to an issue that was fixed two years ago, and calling it out as if it was a different problem than it was.

        It’s good to have discussions about security best practices, but this thread is pointless. This problem is simply not there anymore.

      • FlumPHP@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        3 years ago

        Sending passwords via email Will compromise any passwords sent via email.

        100%. But that is a different problem and a different attack vector than storing passwords in plain text for authentication. When reporting security issues, it’s important to be precise.

      • abhibeckert@lemmy.world
        link
        fedilink
        arrow-up
        3
        arrow-down
        2
        ·
        3 years ago

        Email isn’t end to end encrypted but, but it generally is encrypted. The people who will have it are the sender (who already have the password since they created it) and whoever runs the recipient’s mail server. Which is hopefully someone the recipient trusts.

        From the sounds of it, this was a password that the server randomly generated, so it’s never been used before, and you are forced to reset the password as soon as you use it, so it’ll never be used again and they do treat it as “immediately compromised”.

        Hardly state of the art security, but it also doesn’t really have any major problems… especially since this is for a forum.

  • Kevin@lemmy.world
    link
    fedilink
    arrow-up
    31
    arrow-down
    1
    ·
    3 years ago

    People weren’t really nitpicking.

    • it’s obviously bad to send an email with a plaintext password
    • the website owners had apparently already resolved the issue
    • it does not mean the passwords were stored in plaintext
    • the OP sounds like a skiddie in a bunch of comments and doesn’t seem to understand how most websites with auth work
  • Windex007@lemmy.world
    link
    fedilink
    arrow-up
    15
    arrow-down
    1
    ·
    3 years ago

    Everyone seems more interested in nitpicking the specifics of what OP is saying and are ignoring [the actual point]

    This is the experience working in a professional software development setting, yes.

  • lowleveldata@programming.dev
    link
    fedilink
    arrow-up
    9
    arrow-down
    2
    ·
    3 years ago

    OP of that thread was talking about how (they think) the password was stored in plain text instead of this “tree” you’re talking about. The discussion on that was not a nitpick.

  • BlueBockser@programming.dev
    link
    fedilink
    arrow-up
    9
    arrow-down
    2
    ·
    3 years ago

    Everyone seems more interested in nitpicking

    Actually, not everyone in that thread is nitpicking. There’s one comment that’s just a helpful hint.

    But yes, nitpicking is fun. I’ll see myself out.

  • abhibeckert@lemmy.world
    link
    fedilink
    arrow-up
    10
    arrow-down
    5
    ·
    3 years ago

    Everyone seems more interested in nitpicking the specifics of what OP is saying

    Yep. That’s how security works. You have to nitpick the specifics.

    The reality is nobody has invented a perfectly secure authentication system that is easy to use (for example, allows easy recovery when people forget their password which for any large service will be tens of millions of times per day).

    Attempts have been made - passkeys being the latest one - but they’re not even remotely easy to use as soon as you step slightly out of the most common path (such as using the web browser that is provided by the company you’re logged in with… try to use Chrome with an Apple passkey, or Safari with a Google passkey, and you’re going to stumble into usability issues).

    Passwords are not considered secure wether they’re sent in a plaintext email or not. They can be secure, if used properly, but 99% of users don’t follow best practices. As a result almost every web service in the world is insecure and it’s the nitpicky details that matter.

    Sending a secret to an email address is a standard step during registration for almost any service.

    • jormaig@programming.dev
      link
      fedilink
      arrow-up
      4
      ·
      3 years ago

      But the thing is that you should never have access to the plaintext password and thus you should never be able to receive it in an email. You should store the salted hash of the password instead of the password itself.

      • 8ace40@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        3 years ago

        These kind of forums don’t store the plaintext password, they send an email while in memory, and hash them afterwards. Still bad security, but it’s not storing it in plaintext.

        • jormaig@programming.dev
          link
          fedilink
          arrow-up
          1
          ·
          3 years ago

          But your password should never reach the server. It should be hashed already at the client and then salted at the server with a random hash. Then you store the salted hash

    • JackbyDev@programming.devOP
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      3
      ·
      3 years ago

      When I say “nitpicking the specifics” I mean OP is saying things like the password should never be unencrypted in memory in the same comment as mentioning things like the password in plaintext in the email and folks are more interested in browbeating over the first thing rather than acknowledging the second as a problem. I see this behavior far too often in tech spaces online. People are often more concerned with being pedantic and technically correct than anything else.

  • schmidtster@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    4
    ·
    3 years ago

    If you’re following proper security procedures you wouldn’t be using the same password for anything else, so they are overly concerned about the wrong things while parading being top notch security wise while not doing it themselves.

    Yeah it’s an issue, but only an issue if you’ve set yourself up to be vulnerable.

    • JackbyDev@programming.devOP
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      2
      ·
      3 years ago

      It’s criticism directed at a service provider, not users. Service providers should assume users reuse passwords. Security is about protecting everyone.

      • schmidtster@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        3 years ago

        Than direct it at the service provider? Oh wait it got fixed a while ago.

        Also where does their liability stop? Should they also just assume everyone is compromised? Where does the users onus come into play? I guess they shouldn’t send password resets than, since they should assume that their email is compromised already….

        Yeah that’s actually a terrible idea if they must assume that they must protect everyone. Sorry can’t reset your password your email must be compromised.

        • JackbyDev@programming.devOP
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          1
          ·
          3 years ago

          This is slippery slope bullshit and you know it. I’m not saying providers should have to magically prevent anything. I’m only saying they shouldn’t send you your password in an email. Crazy take, I know.

          Also, with regards to it already being fixed or not, when I made this thread I hadn’t seen anything about that in the other thread. I’m more just annoyed that people want to dunk on people with supposed gotchas while acting like sending a password in an email is okay somehow.

          • schmidtster@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            arrow-down
            1
            ·
            3 years ago

            No it’s not slippery slope in this case, it’s what you’re suggesting and why it’s utter bullshit. But yes of course that’s the obvious defense to take there.

            You’re not only saying that, you said that they need account for everything. Two totally different things. Can’t have X and not have Y.

            Sending a password is okay in quite a few scenarios, you’re talking to broad again her. Also, maybe make sure you know the story before jumping on as well…? You’re making the issues worse not better.

  • ck_@discuss.tchncs.dedeleted by creator
    link
    fedilink
    arrow-up
    3
    arrow-down
    11
    ·
    3 years ago

    A sad truth and sadly not uncommon. Some people seem to get a kick out of showing of how much “smarter” they are than the next person, side tracking the whole conversation in the process. I really don’t get why someone would think that’s called for.