Hey everyone
I am currently setting up LDAP hoping to get a unified authentication solution. My thoughts for this are setting up linux, samba, zimbra, and possibly asterisk (not well supported, hopefully later on)

I have got it working for local logins, but i can not get ssh to work.
Does anybody have any guides, for ideas? Do i need to recompile ssh to support LDAP? Every guide I have found uses PAM, and well Slackware doesn't use PAM (thus posting in the slack forum and not network)

Thanks
-Eric

PS, all Slack boxes are 12 or 12.1

If you're determined, at this stage I think you should be writing the HOWTO, not asking us. You have a major undertaking there, where you hope to have several different authentication procedures agreeing with each other.

Of those protocols, samba is doable (I've done it) Ssh is doable, (I've done it) but I shudder to thing of samba under ssh, let alone integrating in the rest of the stuff you want there. Are you an experienced sysadmin?

LFS (or HLFS) use blowfish passwords which apparently are the most difficult to crack. They host weird people who, like 'The Count' in Sesame Street, take an excessive mathematical interest in such things. Slack I always thought of as a distro where you took it on because you know your stuff, and didn't need or want yum or apt-get.

In short, to quote the Kerryman when asked for directions "If I were you I wouldn't start from here at all!"

I have been using slack now for a number of years and do have quite a lot of experience.
Things I know I can do, once I get my LDAP schema setup the way I want are Samba, local auth, and Zimbra. I have local quth working currently, but I'm having troubles with SSH because everything I have found says in order for SSH to authenticate against an LDAP backend requires PAM, and as you know Slack doesn't have PAM. Without SSH it seems kind of pointless to be continuing on (not really, but a pain I'm trying to get away from).
I don't like managing user accounts in all these different places and thus LDAP.

So, SSH and LDAP? can it be done without PAM?

Thanks

You're asking us and telling us at the same time. If everybody says Pam is needed, then it's likely Pam is needed. It can be installed from source, but every time I hear of pam on a mailing list it's because a luser can't log in to his own box. Have a look at this link

http://www.linuxfromscratch.org/blfs...linux-pam.html

Which is a set of instructions for building pam with several stings in the tail. B(LFS) uses a different directory structure than slack, so watch that. You have to reinstall the shadow package because that needs to link against pam if it's there, IIRC. Which is why users don't get to log in. I never decided security was _that_ important to me.