Hi all, back for more

Ok this is, hopefully, just a quick one.

Su no longer works either from the shell or console. I know I type in the pw correctly but it is always rejected.

However when I logout to the X session manager, select user root, I can login no problem.

So any ideas??

Thanks in advance, all advice much appreciated as always.

BashTin.

PS: On slack 11.0

caps lock , num lock , different keyboard layout?

Have you tried 'su -' instead of just 'su'?

caps lock..... no
num lock..... no
different keyboard layout....no. Tried all those under the settings menu, just the same result.

Have you tried 'su -' instead of just 'su'? Yeah tried that, still the same.

Incidentally, and I know I shouldn't, but if I just type the pw on the command line it is correct so it tends to suggest it is an authentication issue rather than an input issue, wouldn't you think?

Thanks, BashTin.

I would say it is either an authentication issue (pam may be blocking su to root) or something in your environment is causing you to immediately log out (that was why my first question). Look at http://www.redhat.com/docs/manuals/e...rivileges.html for more info. I know it is Red Hat and not Slackware, but the concepts should be the same.

slackware doesn't have pam, but i think an immediate logout is our best bet here.

Su sbit removed ?
What says:

This is the result of 'ls -l /bin/su'

-rws--x--x 1 root root 31776 2006-08-23 04:08 /bin/su*

Thanks for all the replies so far.

Ater I type the pw in all I get is the message 'sorry'.

BashTin.

It could be your system has been hacked and a malicious su is installed.

You may want to try rootkit hunter for figuring it out: http://sourceforge.net/projects/rkhunter/

Run rkhunter and comes up clean, except a few warnings about httpd time services.

Are other files in /bin also having a modify time around 2006-08-23 04:08 ?

jlliagre edited result of 'ls -lt /bin' and (don't flame me now) but this has been irritating me a while but I have just had to login to root from x session manager. BUT, if I recall correctly, this issue seemed to arise after I recompiled the kernel...

60 -rwsr-xr-x 1 root root 60576 2006-09-25 16:48 mount*
20 -rwxr-xr-x 1 root root 18368 2006-09-25 16:48 setterm*
452 -rwxr-xr-x 1 root root 459880 2006-09-25 16:48 sln*
32 -rwsr-xr-x 1 root root 31796 2006-09-25 16:48 umount*
52 -rwxr-xr-x 1 root root 51364 2006-09-20 02:46 gzip*
28 -rwxr-xr-x 1 root root 27880 2006-09-18 15:39 bzip2*
8 -rwxr-xr-x 1 root root 7576 2006-09-18 15:39 bzip2recover*
44 -rwxr-xr-x 1 root root 44856 2006-08-23 04:08 login*
32 -rws--x--x 1 root root 31776 2006-08-23 04:08 su*
192 -rwxr-xr-x 1 root root 192720 2006-08-21 12:27 tar*
116 -rwxr-xr-x 1 root root 115580 2006-08-21 12:27 tar-1.13*
32 -rws--x--x 1 root root 29364 2006-08-14 06:20 ping*
28 -rws--x--x 1 root root 26764 2006-08-14 06:20 ping6*
4 -rwxr-xr-x 1 root root 3884 2006-08-14 06:19 ipmask*
72 -rwxr-xr-x 1 root root 71984 2006-08-14 06:19 telnet*
68 -rwxr-xr-x 1 root root 66212 2006-08-14 06:18 ftp*

BashTin

Ok sorted it.

Of course the solution was obvious and simple....

change root pw!!

Thanks for all your help and suggestions, BashTin.

Ok sorted it.

Of course the solution was obvious and simple....

change root pw!!

Thanks for all your help and suggestions, BashTin.