ssh setup slack 9.1

rotvogel · 05-05-2004, 03:58 PM

I think there is something wrong with your password file. The first error you gave us indicated that there was missing an user. That user should have been in your password file. It was in all Slack installations I did since this feature appeared in OpenSSH (priv seperation).

Next thing I read is a message that you had to restore the password file.

After you did that you get a message to go away because you don't exist. That's the password file as well if I remember well. You probably messed up your password file.

shilo · 05-05-2004, 04:30 PM

I agree. Why don't you post your /etc/passwd file and maybe that will help.

nixel · 05-06-2004, 07:26 AM

/etc/passwd:

Code:

root:x:0:0::/root:/bin/bash
bin:x:1:1:bin:/bin:
daemon:x:2:2:daemon:/sbin:
adm:x:3:4:adm:/var/log:
lp:x:4:7:lp:/var/spool/lpd:
sync:x:5:0:sync:/sbin:/bin/sync
shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown
halt:x:7:0:halt:/sbin:/sbin/halt
mail:x:8:12:mail:/:
news:x:9:13:news:/usr/lib/news:
uucp:x:10:14:uucp:/var/spool/uucppublic:
operator:x:11:0:operator:/root:/bin/bash
games:x:12:100:games:/usr/games:
ftp:x:14:50::/home/ftp:
smmsp:x:25:25:smmsp:/var/spool/clientmqueue:
mysql:x:27:27:MySQL:/var/lib/mysql:/bin/bash
rpc:x:32:32:RPC portmap user:/:/bin/false
sshd:x:33:33:sshd:/:
gdm:x:42:42:GDM:/var/state/gdm:/bin/bash
pop:x:90:90:POP:/:
nobody:x:99:99:nobody:/:
nixel:x:1000:100::/home/nixel:/bin/bash
shyet:x:1001:100:,,,:/home/shyet:/bin/bash

ringwraith · 05-06-2004, 07:50 AM

And you are using user nixel or shyet when you ssh localhost?

http://www-106.ibm.com/developerwork...-cranky37.html

nixel · 05-06-2004, 08:00 AM

yes i am.

Cerbere · 05-07-2004, 12:30 AM

I don't know if this is relevant (and don't see how it could be), but in my /etc/passwd file, the sshd user is listed just after nobody and just before the regular users. So it makes me wonder, did you restore the passwd file by editing it and adding the missing line(s), or by moving an original copy back into place? While your current file seems more correct in the sense that the usernumbers are sorted, it may be causing a problem. I'd be surprised if this were the cause of your problem, but what the heck, it's worth a shot.

Enjoy!
--- Cerbere

nixel · 05-07-2004, 09:14 AM

cerbere, thanks for te response, ill certainly try to move it once i get home (@school now). as far as the passwd file. i made a backup before i did any drastic changes to the file so i basically just renamed 'passwd-' to 'passwd' overwriting the existing passwd that i had a problem with. but ever since then ive been getting errors from DIFFERENT programs saying 'u know user id 1000' which is strange. i have never seen this error before. i see these errors when i exit X. and every program i access such as gaim, xine and/or xmms it has this error. i think its related to the error im having in ssh. any more suggestions people? thanks in advance.

nixel · 05-07-2004, 12:02 PM

ok..update on the situation..i can log on when im root 'ssh localhost' so i know the daemon is up and running.
but im still getting the "you dont exist, go away!" msg when i try to log in from any other user. when i log out of X i see something like this on the screen:

Code:

(process:1313): GLib-WARNING **: getpwuid_r(): failed due to unknown user id (102)

** (process:1313): WARNING **: Owner of /tmp/orbit-somebody is not the current user
could not get user name from user id

(xchat:1506): GLib-WARNING **: getpwuid_r(): failed due to unknown user id (102)
cannot find user w/ uid 102
cannot find user w/ uid 102

ive changed the uid to see if that would do anything but theres no luck. anyone know why ssh works only in root and not on regular user accounts? =\

shilo · 05-07-2004, 01:06 PM

Messing around with /etc/passwd can cause quite a bit of headaches, as I'm sure you already know. This may help. I do it all the time and have never had any problems with it:

1) Reboot to console. Not sure if you have to, but I know it doesn't hurt.
2) Login as root
3)

Code:

cd /tmp
rm -r *

Make SURE you are in /tmp. You can accidently delete a bunch of stuff with that command if you aren't careful.
4) Reboot into whatever you like, e.g. console, X, whatever.
5) See if your problem isn't solved.

May just be that the userid's that are stored in /tmp are all messed up now. This will fix that, for sure.

Also, I am pretty crappy at reading /etc/passwd , so I could be wrong here, but It looks to me like you don't have a user with userid 102. That's your problem. Maybe deleting everything in /tmp will correct this problem for you.

Hope this helps,

nixel · 05-07-2004, 03:57 PM

shilo, i deleted everything in my /tmp folder logged in and logged back out of X and 'xmms-centro.0=' wasnt there anymore...but 'xmms-somebody.0=' is still there. i dont really know whats going on.

and uid 102...i had changed that in my passwd file to see if it would make any difference. but obviously it hasnt. getting discouraged here..dont really know what i did...probably just going to re-install slack and compile 2.6.5 again making sure whats working and whats not after every change i make on the system.

shilo · 05-07-2004, 04:52 PM

So, you deleted everyhting in /tmp and rebooted. Then you tried to log in as a user and tried

Code:

ssh localhost

What was your error message now?

nixel · 05-07-2004, 04:57 PM

shilo, same thing. "you dont exist, go away!"

shilo · 05-07-2004, 05:03 PM

use ctrl-alt-f1 and see if there are error messages like the ones you saw before when logging out of X. What then?

Shade · 05-07-2004, 07:20 PM

When you restored your passwd file, you changed what your computer thinks is your UID number. SSH uses the UID over the Username, so since your ID number of 102 doesn't exist in passwd, it mucks things up.

This may not help, but I'd try this as root...

Code:

cd /home/
chown -R nixel nixel/*

That may fix this by reassigning the UID that passwd states to every file in your home directory as its owner.

--Shade

nixel · 05-07-2004, 07:30 PM

shade that did it thanks! thanks for everyones help!!! now i can log on regular user...

NOW.....if it aint one problem in slackware....its another...ill post a new thread on it...

THANKS AGAIN EVERYONE! finally...;D