[SOLVED] PAM slackware-current

Panther_ · 05-23-2020, 10:36 AM

Hello,

I'm having trouble logging in to the system (slackware-current). I have updated the system to the current version. After restart I receive a message:

Code:

login incorrect

There are user and root accounts in the system.

My config:

Code:

#/etc/pam.d/login

#%PAM-1.0
auth            required        pam_securetty.so
# To set a limit on failed authentications, the pam_tally2 module
# can be enabled. See pam_tally2(8) for options.
#auth            required        pam_tally2.so deny=4 unlock_time=1200
auth            include         system-auth
auth            include         postlogin
account         required        pam_nologin.so
account         include         system-auth
password        include         system-auth
session         include         system-auth
session         include         postlogin
session         required        pam_loginuid.so
session         optional        pam_ck_connector.so nox11

Any suggestions?
I will add that I have been using slackware since version 8.0. It's been a long time. However, PAM will probably not allow me to continue using it.

ponce · 05-23-2020, 10:56 AM

is this a full installation? have you installed the new packages added to current in the last days?

Panther_ · 05-23-2020, 11:37 AM

Thank you for your interest,

this is not a full installation. This is an uninterrupted current since 2011. Constantly updated. The computer is for home use.

As suggested in the ChangeLog file, I installed pam, cracklib, and
libpwquality and new shadow.

I have default settings for PAM. Everyone writes that after the update, pam works imperceptibly.
Unfortunately, this is not the case with me.
I tried to replace grooup files by deleting my entries.
I also wanted to add a new user to try to solve the problem. PAM does not allow you to give it a password or permissions.

I do all this on a mounted system.

I don't know where to start?

I do not want to go the road - reinstallation does not work ...

ponce · 05-23-2020, 11:44 AM

maybe you are missing some dependencies: I would try with libtirpc and krb5, if you haven't installed them already.

but if you decide to do partial installations you should be able to handle dependencies yourself...

Panther_ · 05-23-2020, 12:23 PM

You know, my system is a bit of a minimalist version.
I did not have these packages installed. I was probably looking through ChangeLog carelessly ...

You are great man! Thank you very much for your time and problem solution :-)
It was nice to read the message:

Code:

Welcome to Linux 5.4.41 i686 (tty1)

login: 
Password:
Last failed login: Sat May 23 18:40:03 CEST 2020 on tty6
There were 39 failed login attempts since the last successful login.
Last login: Wed May 20 12:06:53 on /dev/tty1

dalacor · 05-24-2020, 06:49 AM

Have you found using a minimal install of Slackware easy to maintain in terms of upgrades. I tried to setup a minimal Slack install this weekend and a: ran into the same problem you ran into - I was missing the libtirpc package and b: I discovered that even though my original install worked fine, I had to install new packages (pam, cracklib and
libpwquality) in order to login after upgrading existing Slackware packages.

But reading your post, I see that you have been running a minimal Slackware Current since 2011. I just wondered if you find regularly find issues with updating Slackware over the years where you have to install new packages using slackpkg install-new or you have to add missing existing packages such as libtirpc to get a Slackware upgrade to work when you reboot after running slackpkg upgrade-all

Panther_ · 05-24-2020, 03:24 PM

There are no major problems updating slackware. Regardless of whether you have the full version or a combination of selected packages.

I made the first installation of slackware from a cd attached to a Linux magazine. The process of installing and configuring the system was well described there. They have already installed the system for the first time without selected groups of packages. And that's how I stayed.

With the development of distribution, some packages are riddled, others are added to the system, others change names and contents. The changes are described in the ChangeLog.txt and CHANGES_AND_HINTS.TXT files. After freezing current in a stable version, the update is additionally described in UPGRADE.TXT

I don't use slackpkg. Maybe for the first time I will use the new system installation, and then manually remove the unnecessary packages ...
Unfortunately, I have to add new packages manually ...

My way to update:
- rsync to current (this is for updating current to my disk).
- find and upgradepkg to upgrade

willysr · 05-24-2020, 08:03 PM

easier way: slackpkg install-new

dalacor · 05-25-2020, 04:10 AM

I would highly recommend using slackpkg to update slackware and kernels. Far easier.

Thank you for your feedback. I will see how my minimal install fares. I guess I just chose a bad time trying this out as it co-incided with the arrival of PAM.

Alien Bob · 05-25-2020, 07:43 AM

Quote:

Originally Posted by dalacor

I would highly recommend using slackpkg to update slackware and kernels. Far easier.

I would highly recommend not to use slackpkg to upgrade your kernels, unless you have a very simple setup (using the huge kernel, no initrd, no LUKS/LVM/RAID)...

I have the kernel-modules and kernel-generic blacklisted and manually 'installpkg' a new kernel alongside my running kernel. Then I create a new initrd to accompany the new kernel and its modules. Then I update (e)lilo and make sure that I can always boot the latest (new) kernel and the previous kernel. That way, I am sure that there will always be a kernel in the boot menu that I know is working.
Finally I removepkg the oldest kernel (keeping two), its modules and its initrd.

ehartman · 05-25-2020, 10:31 AM

Quote:

Originally Posted by Alien Bob

Finally I removepkg the oldest kernel (keeping two), its modules and its initrd.

I even often keep three, which are labelled vmlinux-bak (the sure to be working backup kernel), vmlinux (the normal running one) and vmlinux-new (the newest, not really completely trusted yet).
They are in the lilo config under those names, but are sym-links to the actual (versioned) kernel files. Note that "vmlinux" is custum-built, so doesn't need an initrd

cwizardone · 05-25-2020, 10:58 AM

Quote:

Originally Posted by Alien Bob

I would highly recommend not to use slackpkg to upgrade your kernels, unless you have a very simple setup (using the huge kernel, no initrd, no LUKS/LVM/RAID)...

I have the kernel-modules and kernel-generic blacklisted and manually 'installpkg' a new kernel alongside my running kernel. Then I create a new initrd to accompany the new kernel and its modules. Then I update (e)lilo and make sure that I can always boot the latest (new) kernel and the previous kernel. That way, I am sure that there will always be a kernel in the boot menu that I know is working.
Finally I removepkg the oldest kernel (keeping two), its modules and its initrd.

What he said!

chrisretusn · 05-25-2020, 11:14 AM

Quote:

Originally Posted by Alien Bob

I would highly recommend not to use slackpkg to upgrade your kernels, unless you have a very simple setup (using the huge kernel, no initrd, no LUKS/LVM/RAID)...

I have the kernel-modules and kernel-generic blacklisted and manually 'installpkg' a new kernel alongside my running kernel. Then I create a new initrd to accompany the new kernel and its modules. Then I update (e)lilo and make sure that I can always boot the latest (new) kernel and the previous kernel. That way, I am sure that there will always be a kernel in the boot menu that I know is working.
Finally I removepkg the oldest kernel (keeping two), its modules and its initrd.

Agree with Alien Bob. I have four installations; one desktop, two laptops and a VirtualBox vm, all Slackware64-current. I also run with two kernels on each with the exception of the virtual machine. This is my clean install box and uses the huge kernel. In this case I do let slackpkg handle the upgrading to the kernel modules.

I do it a bit differently. I don't change my lilo.conf, my changes are done with the symlinks. Each computer has its own specific /etc/mkinitrd.conf file. The default boot is the running kernel, the other boot option is the last working kernel; named "Slackware64" and "LastWorking". In /boot/ I have the standard links for the kernel (System.map, config, vmlinuz) and another set of links to the LastWorking kernel (System.map-working, config-working, vmlinux-working). I occasionally run with a third kernel for "Testing". When I upgrade the kernel, I remove the Lastworking kernel, the currently running kernel is symlinked to the LastWorking kernel. The new kernel (kernel-generic, kernel-headers, kernel-modules, kernel-source) is manually installed and by default takes the default links formerly used by the running kernel. I do not install the huge kernel.

I then run 'mkinitrd -F -k 5.4.42' for the new kernel; then
'mkinitrd -F -k 5.4.41 -s initrd-working-tree -o initrd-working.gz'; then
lilo

The "-F" tells mkinitrd to use /etc/mkinitrd.conf

dalacor · 05-25-2020, 07:19 PM

I stand corrected. I currently update Slackware in a two stage process. I do slackware install-new and slackware upgrade-all, reboot the system and then upgrade just the kernel using slackware upgrade-all by removing kernels from blacklist. However, I am aware that this is not recommended procedure. Having said that, as I am planning to move all my Slack boxes to virtual machines I don't really see this as a problem for me as I can create a hypver-v checkpoint then do my upgrades and if something goes wrong I can revert to that snapshot.

I was focusing more on the point where Panther is using rsync to connect to current, then find and installpkg. It would be so much easier to use slackpkg to upgrade existing packages and install new packages. Using rsync and install seems a very time consuming way to do it.

zdolar · 06-19-2020, 08:45 AM

Hi!

Have the same issue (login incorrect) on my VirtualBox slackware64-current slackpkg install-new and upgrade-all on 27.5.2020 (last package udated zstd-1.4.5)
Have RO access to files on that image. So I can debug PAM and other config files, see logs, etc.
How to solve this, as I can probably boot to single user mode with:
boot: linux init=/bin/sh
/sbin/mount /dev/sdxy / -o remount,rw

But network will not work.

Is it possible to solve that?