FWIW, it’s not fixed as of today. (Maybe Larian patched the vendor code 3 years ago and it resurfaced when they installed a new version?) Regardless, the post in question was bad reporting, as I detailed in another comment here.
FWIW, it’s not fixed as of today. (Maybe Larian patched the vendor code 3 years ago and it resurfaced when they installed a new version?) Regardless, the post in question was bad reporting, as I detailed in another comment here.
elbarto777@lemmy.world 8 months ago
Are you saying that the parent poster is giving incorrect information?
ono@lemmy.ca 8 months ago
Yes, mosiacmango’s comment echoed what others had said earlier (right down to specific words that I used in the original thread and here), but then went further with this conclusion:
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, 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.
____@infosec.pub 8 months 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.