From: Thorsten Kukuk <kukuk@suse.com>
To: distributions@lists.linux.dev
Subject: lastlog2 as Y2038 safe lastlog replacement
Date: Tue, 21 Mar 2023 13:52:59 +0000 [thread overview]
Message-ID: <20230321135259.GA32352@suse.com> (raw)
Hi,
as already written, there are several Y2038 problems with glibc even on
some 64bit architectures
(https://www.thkukuk.de/blog/Y2038_glibc_utmp_64bit/).
I wrote now "lastlog2" as Y2038 safe lastlog replacement.
All the informations can be found in my blog: https://www.thkukuk.de/blog/Y2038_glibc_lastlog_64bit/
and the code on github: https://github.com/thkukuk/lastlog2
In short: lastlog2 consist of a library, which provides a generic API
for this, a PAM module, so that no application needs to be touched, and
a lastlog2 application similar to 'lastlog' to display and maintain the
data.
sqlite3 is used as backend, a robust, well maintained database.
Thorsten
--
Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies
SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nuernberg, Germany
Managing Director: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
(HRB 36809, AG Nürnberg)
reply other threads:[~2023-03-21 13:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230321135259.GA32352@suse.com \
--to=kukuk@suse.com \
--cc=distributions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).