okay, so i have a working slack 9 box (2.4.20) boots fine, ssh works great

.. i upgrade to 2.6.0, works reasonably fine. (slight issues with the NIC module, but i fixed that with some info hunting)

upgrade to 2.6.3, all seems to be okay. only, SSH has stopped working right

sshd -D works and lets me interact that way, but this is hardly a longterm
solution. i generated a new set of keys, no go.

sshd -d takes up a terminal, but runs okay.


so... anyone have any tips/help they can give me?

random info:

clean 2.6.3 compile, removed only sound/usb support
added in only NIC/reiserfs/xfs support
all else is default

I know this is not much help, but sometimes it's good to hear.
I upgraded to 2.6.3 and my ssh was working fine. It may have somthing
to do with how you compiled your kernel.

I can send you the kernel conf from mine if it helps, and you can see whats different. Just a thought.

Ade

Any log entries in /var/log/messages that are interesting?

all i'm finding in any of the logs (syslog to be exact) is a "daemon() failed: success" message for sshd, quite a few times. with no real clue as to why it's failing

what i've done since the first post:

complete recompile without stripping the usb/sound
and only adding in the 2 things i _need_
(reiserfs and NIC support)


no sshd

switching back to 2.4.20 (slack9 default kernel) or 2.6.0 and sshd works flawlessly, so here's whats been done

last 2.6.3 compile:

make mrproper
make menuconfig

added nic support (3c509 etherlink3)
added Reiserfs support
saved, quit

make clean
make bzImage
make modules
make modules_install


copying the two required files over to /boot and doing the rename/symlink/lilo thing

reboot

now, with a near bone stock kernel config, one would imagine that sshd would work without any problem. yet it does not o_O

doing the above compile steps with 2.6.0 works fine.

i am forced to wonder :\

Try adding more -d (up to three can be used) to see if you get any more info on what the problem is.
Also try the -t option to check the sanity of your config and keys.

-t doesn't seem to do anything, much the same as just straight up "sshd"
-d checks keys, does the rest of the key thing, and then occupies a VT
it'll do that for each terminal i use it on (no errors)
yet, when not using -d or -D, it fails with a terminal error that isn't reported

i did get it to report something about not being able to find/use the keys
though i'm not sure how i did that

on a side note: editing the config and uncommenting the defaults (while leaving them the same) tells me it can't find the ssh2 keys even though they're in the right place

i did generate a new set of keys and placed them into all of the "known" locations, i still get nothing helpful :\ and i can't seem to find a logging option anywhere. this is greatly annoying me >

reading some obscure manuals found through the glory of google, yeilds me a -e flag

which results in the 'daemon() failed: success' error

alas, this does not help me figure out what the heck is going on.

Don't know if this has anything to do with it, but i don't compile my kernel like that. Thats the 2.4 method as far as i know. I do it like this :

extract kernel source
remove and remake my /usr/src/linux symlink (ln -s linux-2.6.3 linux/)
make menuconfig (change whatever you need to)
make
su -c "make modules_install"
make install

i then copy over the kernel file (cp arch/i386/boot/bzImahe /boot)
and configure and run lilo

It works fine for me. I like you also had problems when compiling using the 2.4 method.

See if that helps

Ade

I'm out of clues.

reverting back to 2.4.* yeilded a harfed sshd, removing everything openssh based and recompiling didn't fix it. killing that off and replacing it with the original slackware version (via installpkg) didn't work.

i'm giving up, wiping the system and going with ext3 or something with a clean install. this time, i'll wait till 2.6.4 or something

thanks anyway

-Tsuki