Hello, Am Dienstag, 11. April 2023, 13:59:27 CEST schrieb Thorsten Kukuk:
I don't know if anybody here did read my blogs about this, but 64bit systems using glibc have still at minimum three Y2038 problems: utmp, wtmp and lastlog.
More details can be found here: https://www.thkukuk.de/blog/Y2038_glibc_utmp_64bit/ https://www.thkukuk.de/blog/Y2038_glibc_wtmp_64bit/ https://www.thkukuk.de/blog/Y2038_glibc_lastlog_64bit/
# grep kukuk planet.ini # (no match) ... which leads to the question if you want your blog added on planet.opensuse.org ;-) If so, please have a look at https://github.com/openSUSE/planet-o-o/ to get added. Back to the main topic of your mail - I'm afraid you've missed a user of /var/log/wtmp: aa-notify -l reads it so that it can display AppArmor events since the last login. What is the recommended replacement for getting the date/time a user logged in last time? (Bonus points if that replacement is easily useable from python ;-) Also, is there a good / recommended way to find out if a system only has the old wtmp, or if it also (or only) has the lastlog replacement?
The old lastlog implementation will be deactivated after gdm get's submitted to Factory and somebody finally accepts openssh.
Note that openQA tests aa-notify -l, which means this step will give the tests some color - at least until I know how to implement support for the lastlog replacement. Regards, Christian Boltz -- [Windows remote herunterfahren] einfach ein Nichtgepatchtes Windows verwenden und einen der tausen Viren, die letztes Jahr die Maschinen runter gefahren haben ;) [Andreas Loesch in suse-linux]