-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
login: warning missing pam_lastlog.so #542
Comments
lastlog is not enabled in linux-pam in buildroot. |
Aha, time for some upstream work then! I'll have a look :-) |
Please also upstream my patch on linux pam to fix path for .pc files when you are already on 🔥 |
Ouch, that one looks a bit nasty ... I think we should revert our change and fix rousette instead, because the Buildroot
|
Upstream patch for |
lazzer@tollan ~/Documents/addiva/infix (main)$ ./output/host/bin/pkg-config --cflags pam Package pam was not found in the pkg-config search path. Perhaps you should add the directory containing `pam.pc' to the PKG_CONFIG_PATH environment variable Package 'pam', required by 'virtual:world', not found lazzer@tollan ~/Documents/addiva/infix (main)$ |
How do find output/ -name.pc looks like? My (relevant parts) looks like: output/host/x86_64-buildroot-linux-gnu/sysroot/lib/pkgconfig/pamc.pc output/host/x86_64-buildroot-linux-gnu/sysroot/lib/pkgconfig/pam.pc output/host/x86_64-buildroot-linux-gnu/sysroot/lib/pkgconfig/pam_misc.pc output/host/x86_64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/dbus-cxx-2.0.pc output/host/x86_64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/libtirpc.pc output/host/x86_64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/libnetfilter_cthelper.pc output/host/x86_64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/libnetfilter_conntrack.pc output/host/x86_64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/libuev.pc output/host/x86_64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/ext2fs.pc output/host/x86_64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/avahi-core.pc output/host/x86_64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/libbsd.pc output/host/x86_64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/libpcre2-8.pc output/host/x86_64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/libsyslog.pc output/host/x86_64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/glib-2.0.pc output/host/x86_64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/popt.pc output/host/x86_64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/libassuan.pc output/host/x86_64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/sysrepo.pc output/host/x86_64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/libpcre2-posix.pc output/host/x86_64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/json-c.pc ..... |
Interesting, here's my output, notably from Buildroot (recently branched from) master: ~/src/buildroot(linux-pam-options)$ find output/staging/ -name '*.pc'
output/staging/usr/lib/pkgconfig/libcrypt.pc
output/staging/usr/lib/pkgconfig/libxcrypt.pc
output/staging/usr/lib/pkgconfig/python-3.12-embed.pc
output/staging/usr/lib/pkgconfig/fmt.pc
output/staging/usr/lib/pkgconfig/python3.pc
output/staging/usr/lib/pkgconfig/libsyslog.pc
output/staging/usr/lib/pkgconfig/zlib.pc
output/staging/usr/lib/pkgconfig/pam.pc
output/staging/usr/lib/pkgconfig/pam_misc.pc
output/staging/usr/lib/pkgconfig/python3-embed.pc
output/staging/usr/lib/pkgconfig/spdlog.pc
output/staging/usr/lib/pkgconfig/python-3.12.pc
output/staging/usr/lib/pkgconfig/pamc.pc
output/staging/usr/lib/pkgconfig/expat.pc
output/staging/usr/lib/pkgconfig/openssl.pc
output/staging/usr/lib/pkgconfig/libssl.pc
output/staging/usr/lib/pkgconfig/libffi.pc
output/staging/usr/lib/pkgconfig/libcrypto.pc Lemme have a look around the tree. |
Found it, root cause is:
With it unset, as in Infix' defconfigs, I get the same as you: ~/src/buildroot(linux-pam-options)$ find output/staging/ -name '*.pc'
output/staging/usr/lib/pkgconfig/libcrypt.pc
output/staging/usr/lib/pkgconfig/libxcrypt.pc
output/staging/usr/lib/pkgconfig/python-3.12-embed.pc
output/staging/usr/lib/pkgconfig/python3.pc
output/staging/usr/lib/pkgconfig/libsyslog.pc
output/staging/usr/lib/pkgconfig/zlib.pc
output/staging/usr/lib/pkgconfig/python3-embed.pc
output/staging/usr/lib/pkgconfig/python-3.12.pc
output/staging/usr/lib/pkgconfig/expat.pc
output/staging/usr/lib/pkgconfig/openssl.pc
output/staging/usr/lib/pkgconfig/libssl.pc
output/staging/usr/lib/pkgconfig/libffi.pc
output/staging/usr/lib/pkgconfig/libcrypto.pc
output/staging/lib/pkgconfig/pam.pc
output/staging/lib/pkgconfig/pam_misc.pc
output/staging/lib/pkgconfig/pamc.pc Since there's no point really in maintaining a difference beteen
Which is the default, so dropping the line entirely would be equivalent. |
Backport pam-lastlog build fix from latest Buildroot master and enable in all defconfigs to fix syslog warning: login[2819]: PAM unable to dlopen(/lib/security/pam_lastlog.so) Fixes #542 Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
Backport pam-lastlog build fix from latest Buildroot master and enable in all defconfigs to fix syslog warning: login[2819]: PAM unable to dlopen(/lib/security/pam_lastlog.so) Fixes #542 Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
Backport pam-lastlog build fix from latest Buildroot master and enable in all defconfigs to fix syslog warning: login[2819]: PAM unable to dlopen(/lib/security/pam_lastlog.so) Fixes #542 Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
The PAM plugin lastlog, previously used (optional) by Netopeer2 and Rousette, does not rotate /var/log/lastlog, and since we don't have cron and logrotate this can potentially fill up /var. This patch disables pam_lastlog.so from the build and drops the two matching session lines for both Netopeer2 and Rousette. Both still log user access to sysrepo, so no critical functionality is lost. Follow-up to issue #542 Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
The PAM plugin lastlog, previously used (optional) by Netopeer2 and Rousette, does not rotate /var/log/lastlog, and since we don't have cron and logrotate this can potentially fill up /var. This patch disables pam_lastlog.so from the build and drops the two matching session lines for both Netopeer2 and Rousette. Both still log user access to sysrepo, so no critical functionality is lost. Follow-up to issue #542 Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
Fixes the following recurring login warning in syslog. (We cannot use pam_lastlog.so since it does not rotate its /var/log/lastlog file.) login[2819]: PAM unable to dlopen(/lib/security/pam_lastlog.so): /lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory Follow-up to issue #542 Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
Fixes the following recurring login warning in syslog. (We cannot use pam_lastlog.so since it does not rotate its /var/log/lastlog file.) login[2819]: PAM unable to dlopen(/lib/security/pam_lastlog.so): /lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory Follow-up to issue #542 Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
The text was updated successfully, but these errors were encountered: