You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current log can be abused and saves data that should not be stored for normal users. If you mistype a password, well now the site forever has your IP, which should not be the case. This can be fixed while keeping the data that is needed and make the log more useful for staff reviewing it.
Add a nullable boolean column, verified login, store null for unchecked, 0 for not that user, and 1 for was that user.
The user has a week before it auto ticks the not me option.
PM and email sent links them to a review screen that queries the failed login table and they can review there
Allow deletions of ones they say is them, however, this could be abused by the hijacker, so we must require the active 2fa to have been enabled from before that failed attempt.
Backups should be changed to only store the "wasn't me" rows, ensuring that even the backup does not log the IP needlessly.
Staff page should default to unchecked and not me only, can allow admin to view all not deleted, mod does not need this ability.
The requirement of 2fa being active before is important, otherwise a hijacker could login and delete the evidence. With 2fa being required before, the only way they could hijack and delete evidence is if they have access to either a recovery code or the 2fa device itself, of which is an entirely different issue. If they enabled it after hijacking the account here they could only mask it, but the investigation of the compromised account could still pull up that data.
A rogue staff with password reset abilities could easily abuse the current feature and effectively enable logging even on sites that follow UNIT3D's desire for not logging such information. Users have reported this happening on some sites too and vanilla UNIT3D needs to protect this from happening the best they can.
Upvote & Fund
We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed.
Thank you in advance for helping prioritize & fund our backlog.
The text was updated successfully, but these errors were encountered:
The current log can be abused and saves data that should not be stored for normal users. If you mistype a password, well now the site forever has your IP, which should not be the case. This can be fixed while keeping the data that is needed and make the log more useful for staff reviewing it.
The requirement of 2fa being active before is important, otherwise a hijacker could login and delete the evidence. With 2fa being required before, the only way they could hijack and delete evidence is if they have access to either a recovery code or the 2fa device itself, of which is an entirely different issue. If they enabled it after hijacking the account here they could only mask it, but the investigation of the compromised account could still pull up that data.
A rogue staff with password reset abilities could easily abuse the current feature and effectively enable logging even on sites that follow UNIT3D's desire for not logging such information. Users have reported this happening on some sites too and vanilla UNIT3D needs to protect this from happening the best they can.
Upvote & Fund
The text was updated successfully, but these errors were encountered: