LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-20-2020, 01:47 PM   #121
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware14.2 64-Bit Desktop, Devuan 2.0 ASCII Toshiba Satellite Notebook
Posts: 2,925

Rep: Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840

Quote:
Originally Posted by hitest View Post
There was a warning to run slackpkg install-new when you install Pam and the other updates.
Not sure if that was addressing me; but to clarify I just downloaded --Current again - created a new iso and did a fresh install
 
Old 05-20-2020, 01:48 PM   #122
hitest
Guru
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD, Debian
Posts: 6,304

Rep: Reputation: 2549Reputation: 2549Reputation: 2549Reputation: 2549Reputation: 2549Reputation: 2549Reputation: 2549Reputation: 2549Reputation: 2549Reputation: 2549Reputation: 2549
Quote:
Originally Posted by Jeebizz View Post
Not sure if that was addressing me; but to clarify I just downloaded --Current again - created a new iso and did a fresh install
Ah nevermind. Heh.
 
Old 05-20-2020, 02:01 PM   #123
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware14.2 64-Bit Desktop, Devuan 2.0 ASCII Toshiba Satellite Notebook
Posts: 2,925

Rep: Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840
The only thing I can think of that might have broke it was me editing /etc/group , like I have always done I don't know...
 
Old 05-20-2020, 02:31 PM   #124
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware14.2 64-Bit Desktop, Devuan 2.0 ASCII Toshiba Satellite Notebook
Posts: 2,925

Rep: Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840
Talking Jeebizz you dumbass

Ok I am officially retarded - I in my zeal in editing /etc/group adding myself to shadow - thats what did it, this time I didn't and all is well. I can log into my created account, and root in tty2 3 4. I accept any and all poking fun/insults coming my way

Last edited by Jeebizz; 05-20-2020 at 02:38 PM.
 
4 members found this post helpful.
Old 05-20-2020, 02:32 PM   #125
denydias
Member
 
Registered: Dec 2013
Distribution: Slackware
Posts: 189

Rep: Reputation: Disabled
Quote:
Originally Posted by mlangdn View Post
All I wanted was for my normal user, michael, to have autologin. This is my personal home computer that only I use. I'm done with this thread. No help here.
Same here for both: autologin for unprivileged users and done with this post.

My hope is that Pat could address this in his always quiet and elegant fashion when he decides to merge sddm into -current.

Before leaving for good, one comment:

Eric is a great guy. I admire him so much. From his baking skills to the way he provides us with tons of awesome bits. This is not going to change.

That being said, when it comes to issues that he has a strong opinion about, there is very little to no chance an individual use case could touch him. This could be frustrating for the ones facing that unfortunate use case, but I understand his point in the sense that those ones could act by themselves at anytime and do not depend on him to fix the thing.

Over and out.
 
3 members found this post helpful.
Old 05-20-2020, 02:53 PM   #126
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,248

Rep: Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942
Quote:
Originally Posted by denydias View Post
Same here for both: autologin for unprivileged users and done with this post.

My hope is that Pat could address this in his always quiet and elegant fashion when he decides to merge sddm into -current.

Before leaving for good, one comment:

Eric is a great guy. I admire him so much. From his baking skills to the way he provides us with tons of awesome bits. This is not going to change.

That being said, when it comes to issues that he has a strong opinion about, there is very little to no chance an individual use case could touch him. This could be frustrating for the ones facing that unfortunate use case, but I understand his point in the sense that those ones could act by themselves at anytime and do not depend on him to fix the thing.

Over and out.
Maybe I missed it, but I haven't noticed Eric saying he's not interested in making sure autologin and unprivileged users working on sddm (autologin is supposed to work with sddm, but based on a previously posted sddm bugreport, it seems that unprivileged might require some workarounds and isn't fully supported with sddm). There has just been a very loud conversation about logging in via root that he has strong feelings about and that seems to have drowned out other conversations. It might be worth taking the autologin discussion to his blog (where he prefers talk about ktown) or at least opening up a new topic so you can separate the noise about root logins from the autologin issue.

That being said, according to Arch, it *should* be as simple as creating a new autologin.conf file in /etc/sddm.conf.d/ (assuming the setups are similar enough between Arch and ktown's sddm packages).

Code:
[Autologin]
User=john
Session=plasma.desktop
Maybe this has been tried and fails, but I don't think I've seen any posts documenting it.
 
Old 05-20-2020, 03:12 PM   #127
LuckyCyborg
Member
 
Registered: Mar 2010
Posts: 683

Rep: Reputation: 462Reputation: 462Reputation: 462Reputation: 462Reputation: 462
Quote:
Originally Posted by bassmadrigal View Post
That being said, according to Arch, it *should* be as simple as creating a new autologin.conf file in /etc/sddm.conf.d/ (assuming the setups are similar enough between Arch and ktown's sddm packages).

Code:
[Autologin]
User=john
Session=plasma.desktop
Maybe this has been tried and fails, but I don't think I've seen any posts documenting it.
I am truly sorry, but no, it does not work like in Arch, Ubuntu or Fedora - the last being just tested by this friend of mine who helped with my configs, resulting that under Fedora the SDDM is capable to autologin to whatever user (including root) and permitting the manual login to whatever user (including root)

Why the SDDM from Slackware with PAM does not work like the ones from Arch, Ubuntu or Fedora?

After my friend, because the Slackware decided to enforce the securetty for it, which practically you should read: the SDDM is actively denied to run as root, because it never will have a secure tty to run from it.

How apparently the SDDM's autologin needs to temporary elevate its privileges to root level before to switch to the particular logged-in user, the securetty enforcement makes SDDM not only to fail to login the root user, but also to autologin to any user, privileged or not.

Also, apparently, the lack of enforcement of securetty is considered a security issue, which I read as: running SDDM as root, even for milliseconds, is considered by Slackware as a security issue, which should be preventive blocked.

Why they think this way, while Arch, Ubuntu or Fedora doesn't, I am unable to explain, having a limited knowledge. Maybe the higher ups will be kind to explain us why is considered a security issue running SDDM as root.

As bottom line, the single way to make SDDM to handle the autologin, is to modify its PAM files, in the ways like I presented in this thread, where basically, like in the other distributions, is not used the securetty enforcement. And if you do that, as collateral effect it accepts also the root logins and the autologin as root.

PS. The PAM configs presented by me are inspired from what Fedora do regarding SDDM.
PS2. I started to wonder if elogind or systemd-logind are smarter than ConsoleKit2 until they are capable somehow to give a "secure tty" to SDDM and that's the real difference.

Last edited by LuckyCyborg; 05-20-2020 at 04:01 PM.
 
Old 05-20-2020, 03:17 PM   #128
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware14.2 64-Bit Desktop, Devuan 2.0 ASCII Toshiba Satellite Notebook
Posts: 2,925

Rep: Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840
CSB breaks --Current

Ok... I found the culprit - it wasn't entirely my fault. I found out what breaks Slackware when trying to login - it is CSB! (Cinnamon slackbuild). I have the --Current downloaded. I figured maybe it would be MSB (Mate slackbuild) or CSB. So what I did, I installed MSB first, logged out, and was able to log into root and my username just fine. So, next I installed CSB, and that is where things break. CSB needs to be recompiled I guess? Note, I downloaded CSB and MSB for --Current from slackware.uk. However I do not know what specific package from CSB breaks the entire system, all I have to go by is the screenshots, and process of elimination, it isn't /etc/group editing, it isn't MSB, but some package from CSB breaks the system.

Click image for larger version

Name:	VirtualBox_Slackware_20_05_2020_15_03_12.png
Views:	5
Size:	24.8 KB
ID:	33234Click image for larger version

Name:	VirtualBox_Slackware_20_05_2020_15_03_52.png
Views:	4
Size:	16.2 KB
ID:	33235
Here after installing MSB, I logged out and logged in just fine




So I then started to install CSB:

Click image for larger version

Name:	VirtualBox_Slackware_20_05_2020_15_06_41.png
Views:	6
Size:	25.0 KB
ID:	33236Click image for larger version

Name:	VirtualBox_Slackware_20_05_2020_15_06_49.png
Views:	7
Size:	20.9 KB
ID:	33237
After installing CSB, I logged out, and that is when I could not login as root or anything else for that matter, so CSB is what breaks --Current with PAM - MSB does not.

Again, I got both from:

http://slackware.uk/csb/current/x86_64/
http://slackware.uk/msb/current/latest/x86_64/

But to be fair, I would like someone to replicate this issue to confirm please. Just install --Current CSB , on a fresh Slackware64 --Current , I would be very interested to know if anyone can replicate this.

Last edited by Jeebizz; 05-20-2020 at 03:19 PM.
 
Old 05-20-2020, 04:03 PM   #129
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,248

Rep: Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942
Quote:
Originally Posted by LuckyCyborg View Post
Also, apparently, the lack of enforcement of securetty is considered a security issue, which I read as: running SDDM as root, even for milliseconds, is considered by Slackware as a security issue, which should be preventive blocked.

Why they think this way, while Arch, Ubuntu or Fedora doesn't, I am unable to explain, having a limited knowledge. Maybe the higher ups will be kind to explain us why is considered a security issue running SDDM as root.
How do you know "they think this way"? 15.0 hasn't been released and PAM has only been in the proper -current for a few days. Just because it isn't working now doesn't mean it was Pat actively trying to deny users from using autologin. Maybe he started out with what he thought was sane defaults and will make adjustments after getting feedback or maybe he intends for the system to be more secure. We won't know unless he chimes in or if updates are pushed out.
 
3 members found this post helpful.
Old 05-20-2020, 04:10 PM   #130
Pithium
Member
 
Registered: Jul 2014
Location: Vancouver, WA
Distribution: Slackware 14.2/current
Posts: 40

Rep: Reputation: Disabled
Quote:
Originally Posted by LuckyCyborg View Post
I am truly sorry, but no, it does not work like in Arch, Ubuntu or Fedora - the last being just tested by this friend of mine who helped with my configs, resulting that under Fedora the SDDM is capable to autologin to whatever user (including root) and permitting the manual login to whatever user (including root)

Why the SDDM from Slackware with PAM does not work like the ones from Arch, Ubuntu or Fedora?

After my friend, because the Slackware decided to enforce the securetty for it, which practically you should read: the SDDM is actively denied to run as root, because it never will have a secure tty to run from it.

How apparently the SDDM's autologin needs to temporary elevate its privileges to root level before to switch to the particular logged-in user, the securetty enforcement makes SDDM not only to fail to login the root user, but also to autologin to any user, privileged or not.

Also, apparently, the lack of enforcement of securetty is considered a security issue, which I read as: running SDDM as root, even for milliseconds, is considered by Slackware as a security issue, which should be preventive blocked.

Why they think this way, while Arch, Ubuntu or Fedora doesn't, I am unable to explain, having a limited knowledge. Maybe the higher ups will be kind to explain us why is considered a security issue running SDDM as root.

As bottom line, the single way to make SDDM to handle the autologin, is to modify its PAM files, in the ways like I presented in this thread, where basically, like in the other distributions, is not used the securetty enforcement. And if you do that, as collateral effect it accepts also the root logins and the autologin as root.

PS. The PAM configs presented by me are inspired from what Fedora do regarding SDDM.
Well that explains why the log messages are the same. When trying to enable autologin, SDDM logs authentication failures to /var/log.

However, on my laptop sddm appears to be running as the root user?
Code:
bash:~$ ps -U root -u root |grep sddm
 3007 ?        00:00:00 sddm
 3008 ?        00:00:00 sddm.bin
 3159 ?        00:00:00 sddm-helper
I'm also out of my comfort zone. I just wanted to identify where it was failing, because I didn't think this was something Eric could solve through ktown packages. I guess it's time to read up on PAM and how it actually works, because it sounds like it changes how things function.
 
1 members found this post helpful.
Old 05-20-2020, 07:45 PM   #131
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 2,543

Rep: Reputation: 801Reputation: 801Reputation: 801Reputation: 801Reputation: 801Reputation: 801Reputation: 801
Quote:
Originally Posted by Richard Cranium View Post
I believe that we have a fundamental difference in opinion that won't be resolved.
It certainly seems that way.

I'll just leave this quote here:

Quote:
Originally Posted by Slackware-HOWTO by Patrick Volkerding v14.2 dated 2016-06-28 s6.4 "User Accounts"
"You should make a user account for yourself. Using "root" as your everyday account is dangerous, and is considered bad form (at the very least) since you can accidentally damage your system if you mistype a command. If you're logged in as a normal user, the effects of bad commands will be much more limited. Normally you'll only log in as root to perform system administration tasks, such as setting or changing the root password, installing, configuring, or removing system software, and creating or deleting user accounts."
I'll never agree with your viewpoint, because your argument is akin to demanding that power saw makers stop equipping their saws with finger guards because they're your fingers and you'll cut them off if you want to.

With that said, I feel sorry for these guys:
Quote:
Originally Posted by mlangdn View Post
All I wanted was for my normal user, michael, to have autologin. This is my personal home computer that only I use. I'm done with this thread. No help here.
Quote:
Originally Posted by denydias View Post
Same here for both: autologin for unprivileged users and done with this post.
Now that we have PAM, we can use solutions which work on other distros.

In case you're still here... does this work for you guys:
https://www.youtube.com/watch?v=ILckBH5JsrI

I haven't tried it, so I don't know if it's what you're looking for, but hopefully it's not too little too late.
 
3 members found this post helpful.
Old 05-20-2020, 08:02 PM   #132
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 2,543

Rep: Reputation: 801Reputation: 801Reputation: 801Reputation: 801Reputation: 801Reputation: 801Reputation: 801
Quote:
Originally Posted by LuckyCyborg View Post
Also, I cannot help to not remember that the Schutzstaffel (SS troops) was formed exclusively from (unpaid) volunteers...
There it is! Mike Godwin was a visionary.
 
7 members found this post helpful.
Old 05-20-2020, 08:27 PM   #133
dchmelik
Member
 
Registered: Nov 2008
Location: USA
Distribution: FreeBSD Unix, Slackware, FreeSlack GNU/Linux, OpenBSD Unix, FreeDOS
Posts: 466

Rep: Reputation: 51
Unhappy

Quote:
Originally Posted by Alien Bob View Post
Everything will keep working as you are used. You will not have to change, modify or update any configuration.
Apparently wishful thinking; after upgrade, I and at least one other on freenode IRC ##slackware couldn't login anymore.

Code:
(xterm) su: error while loading shared libraries: libpam.so.0: cannot open shared object file: No such file or directory
(console!) /bin/login: error while loading shared libraries: libpam.so.0: cannot open shared object file: No such file or directory
Luckily I still had a root xterm and managed to install pam... but some sort of PAM-depended configuration/package even for pure (non-X) console was installed even before the pam package was installed! Things worked after finishing upgrade, but I see things might fail in the future similarly on any upgrade of packages needing new PAM but wasn't installed yet (even network error)... not how things should be!

Is there a way we can just disable PAM for pure (non-X) and X terminals? I hate PAM as much as systemd. If KDE needs it, fine, but for years I've been trying to switch to (Ns)CDE (previously TDE, even since KDE4)... in that case I'd want to maybe just remove PAM/XFCE/KDE...

People were considering Slackware fork or hopefully maybe alternative official version, more for command-line programmers, servers without XFCE/KDE that need more reliable upgrades.

I think this is last straw for me with KDE. As said, 'so it begins:' what will KDE, XFCE break next?

Last edited by dchmelik; 05-24-2020 at 06:57 PM.
 
Old 05-20-2020, 08:40 PM   #134
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,171

Rep: Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396
if you are using CSB, you can simply remove pam, cracklib, and krb5 and use the one in Slackware instead and you should be fine. Make sure to install those 3 files (pam, cracklib, libpwquality) before logging out/rebooting.
 
Old 05-20-2020, 09:48 PM   #135
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,248

Rep: Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942Reputation: 4942
Quote:
Originally Posted by dchmelik View Post
Apparently wishful thinking.

After upgrade, I and at least one other on freenode IRC ##slackware couldn't login anymore.

Code:
(xterm) su: error while loading shared libraries: libpam.so.0: cannot open shared object file: No such file or directory
(console!) /bin/login: error while loading shared libraries: libpam.so.0: cannot open shared object file: No such file or directory
If it is saying that libpam.so is missing, then it seems you didn't do a proper upgrade of -current (did you forget to install-new if using slackpkg?), because libpam.so would've been installed with the pam package.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
a bug in dialog merged with Slackware64 current? duturo1953 Slackware 1 08-23-2017 02:26 PM
/etc/pam.d/system-auth-ac vs. /etc/pam.d/password-auth-ac vs. /etc/pam.d/sshd christr Red Hat 2 08-01-2014 07:08 PM
PAM module:passwd:- how many character validate by pam library amit_pansuria Linux - General 3 10-21-2008 01:19 AM
vsftpd + pam + virtual users - Pam cannot load database file. mdkelly069 Linux - Networking 3 09-22-2004 11:07 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:50 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration