>From the Debian bug report it sounds like this issue was resolved upstream in version 4.14.11 or 4.15.3 or higher. Kinetic includes 4.16, but presumably focal and jammy are affected. I think steps to reproduce would be required to be identified before considering SRU, but I've opened the bug tasks for those releases.
** Tags added: server-triage-discuss ** Also affects: samba (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998355 Importance: Unknown Status: Unknown ** Bug watch added: Samba Bugzilla #14127 https://bugzilla.samba.org/show_bug.cgi?id=14127 ** Changed in: samba Status: Fix Released => Unknown ** Changed in: samba Remote watch: Debian Bug tracker #998355 => Samba Bugzilla #14127 ** Changed in: samba Remote watch: Samba Bugzilla #14127 => Debian Bug tracker #998355 ** Changed in: samba Remote watch: Debian Bug tracker #998355 => Samba Bugzilla #14127 ** Also affects: samba (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: samba (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: samba (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: samba (Ubuntu Kinetic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server/Client Support Team, which is subscribed to samba in Ubuntu. Matching subscriptions: Ubuntu Server/Client Support Team https://bugs.launchpad.net/bugs/1952531 Title: samba: Access Time of File is set to far future: Access: 30828-09-14 04:48:05.477580700 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1952531/+subscriptions -- Mailing list: https://launchpad.net/~enterprise-support Post to : [email protected] Unsubscribe : https://launchpad.net/~enterprise-support More help : https://help.launchpad.net/ListHelp
