Bug #115973 Dual password usages should have a counter per users
| Submitted: | 30 Aug 2024 17:04 | Modified: | 1 Oct 2024 8:13 |
|---|---|---|---|
| Reporter: | Yoann La Cancellera | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Pluggable Authentication | Severity: | S4 (Feature request) |
| Version: | 8.4 | OS: | Any |
| Assigned to: | CPU Architecture: | Any |
[30 Aug 2024 17:04]
Yoann La Cancellera
[31 Aug 2024 13:58]
MySQL Verification Team
Hello Yoann, Thank you for the report and feature request. regards, Umesh
[27 Sep 2024 12:30]
Georgi Kodinov
Thank you for the very reasonable feature request. I have a question: is it enough to just track old password usage since the last restart? Writing something in a disk-based table during login can have a serious performance impact.
[1 Oct 2024 8:13]
Yoann La Cancellera
Storing this information on disk seems overkill to me, especially if it has performance impacts Having the info since the last restart seems reasonable to me Just in case I'm detailing one of my suggestion, it was not clear "- a field in performance_schema.session_connect_attrs" I meant having the password shasum as a row in this table. I'm not saying it's the best idea, it might be problematic to store any password shasum outside of the user table. That way it could have been used to join mysql.user on the current or old password. It felt to be the quickest implementation to me Thanks for your update
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.047 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.