Right, I do believe the “short term” one is securing the database. There are ways to encrypt the data so that actually seeing the whole dataset becomes visible only to the application. Now unsure if the server got compromised, if a MITM happened and how… Hence why there should be public disclosure imo.
Yes the passwords were plain text. But for a reason “stupider” than lack of encryption for the sake of it. MyTUM communicates to TUMOnline by literally authenticating *as* the user. Hence why the plain text. This could have been prevented by the table itself or the database itself being encrypted. And the encryption layer being within the Application.
I wonder if the database password was in an .env file or how they got database access. That part is the, in my honest opinion, inexcusable part. Even more a SysAdmin without MFA and using same password on both places. That is just being reckless. That said the system should enforce MFA and not allow admins without MFA.
Maybe the ITO department is underpaid. Hoping that proper resources get invested in properly protecting the system.
@nimarblu@TU_Muenchen That said, unsure if this was the case or as other say if there was a MITM. I hope ITO makes a public blog post in the future disclosing the whole ordeal for transparency
@ashleywolf@zeeg I do wonder tho, if it’d made the sense to have a toggle so you can see timeline events at the overview too… Sometimes we like to see the correlation of these 🤔
@zeeg@ashleywolf The only piece confusing for me is that the recent to older messages on issues and anywhere else is still top->bottom whereas on the new PR overview it is bottom->top and that can be disorienting.