PAM about to be merged in -current

Alien Bob · 05-18-2020, 04:11 PM

Quote:

Originally Posted by drgibbon

Thanks for the heads up.

So what's the story with ktown if we're running the non-testing packages, wait for updates, or just switch straight over to the testing packages?

I've already updated the ktown repository. Basically 'latest' and 'testing' are now identical so it won't matter which of the two you had configured, you'll get the PAM-fied packages. If you already were using the PAM from Slackware's testing combined with my ktown 'testing' repository, then there's nothing you have to change.

If you did not use PAM before, you will have to do a reinstall of the following packages which are the only ones that want to use PAM: kscreenlocker, plasma-workspace and sddm-qt5. And don't forget to install the new kwallet-pam package.

cwizardone · 05-18-2020, 04:37 PM

Quote:

Originally Posted by bassmadrigal

It's official, and it should go unnoticed by the vast majority of users. Make sure you slackpkg install-new or manually install pam, cracklib, and libpwquality..........

Installed and completely transparent.

garpu · 05-18-2020, 04:38 PM

Is kerberos coming, or did I miss it in the patch notes? Nevermind. We've had that for awhile.

USUARIONUEVO · 05-18-2020, 04:55 PM

Quote:

Originally Posted by garpu

Is kerberos coming, or did I miss it in the patch notes? Nevermind. We've had that for awhile.

you miss krb5 ..is added some weeks ago.

hitest · 05-18-2020, 04:56 PM

Quote:

Originally Posted by cwizardone

Installed and completely transparent.

Yep. Updated my units; it was painless. Many thanks to Mr. Volkerding and the Slackware Team.

USUARIONUEVO · 05-18-2020, 04:57 PM

Hello , i have a little issue after merge PAM , .. i cant use kde4 autologin , i have configured to no enter password everytimes , but now i cant autostart , i see a file under

/etc/pam.d/kde

but i dont know what need to change to make autologin working again.

some idea ?

thanks!

upnort · 05-18-2020, 07:25 PM

Quote:

Otherwise, these changes should be completely transparent and you shouldn't
notice any obvious operational differences.

I was not using the /testing packages. Updating my Current VM was a non event here. No boot or login issues and I noticed -- nothing.

Hat tip Pat!

bassmadrigal · 05-18-2020, 07:35 PM

EDIT: Missed the next page and am way too late with my response.

denydias · 05-18-2020, 10:08 PM

Just PAM-fied my box. All went well except sddm autologin not working anymore. Manual login works fine in console and sddm though. I'll take a look on that later... maybe someone has even solved that in this thread.

Nice work, Pat et all!

RadicalDreamer · 05-18-2020, 11:13 PM

Code:

The list below shows all packages with name matching "pam".

[ Status           ] [ Repository               ] [ Package                                  ]
   installed               ktown                        kwallet-pam-5.18.4.1-x86_64-1alien        
   installed               multilib                     pam-compat32-1.3.1-x86_64-1compat32       
   installed               slackware64                  nss-pam-ldapd-0.9.11-x86_64-1             
   installed               slackware64                  pam-1.3.1-x86_64-1                        
   installed               slackware64                  pam-krb5-4.9-x86_64-1                     
   installed               slackware64                  pamixer-1.4-x86_64-5

It is working good so far.

drgibbon · 05-19-2020, 01:55 AM

Quote:

Originally Posted by Alien Bob

I've already updated the ktown repository. Basically 'latest' and 'testing' are now identical so it won't matter which of the two you had configured, you'll get the PAM-fied packages. If you already were using the PAM from Slackware's testing combined with my ktown 'testing' repository, then there's nothing you have to change.

If you did not use PAM before, you will have to do a reinstall of the following packages which are the only ones that want to use PAM: kscreenlocker, plasma-workspace and sddm-qt5. And don't forget to install the new kwallet-pam package.

Thanks! Today I upgraded two machines running -current, one with ktown and one without, all smooth sailing so far.

teoberi · 05-19-2020, 02:36 AM

Maybe what I felt about PAM was wrong!
I manually installed all the updates (according to ChangeLog from 18.05.2020) and recompiled my packages (including Dovecot) on the test server and everything seems OK.

kgha · 05-19-2020, 03:31 AM

Kudos to Eric for immediately PAMifying his multilib repo and to willysr for doing the same with the msb repo!

denydias · 05-19-2020, 03:31 AM

Quote:

Originally Posted by drgibbon

Thanks! Today I upgraded two machines running -current, one with ktown and one without, all smooth sailing so far.

Same here, -current and latest ktown. Do you use sddm autologin? Is it working there?

Thom1b · 05-19-2020, 03:54 AM

Hi,

Since the last upgrade with pam, the file /etc/suauth seems to be ignored. So "su" has only his default behaviour : asking for user login password. Is there a way to make /etc/suauth work again please?