hi,
first of all thanks for your reply. Of course I did have a look at sadms.
I have it up running and it is working quite reliable. Anyway there's
something that keeps me worried. I tried analyzing the network traffic
and figured out it's a big mess :) Hard to trace, hard to follow hard
to understand. A timeline schematic showing the complete login process
would be superb. Unfortunately all the documentation consists of some
poorly described screenshots. Maybe the winbind/samba documentation
has more information to offer, I'll check that asap. As far as I could
see it is using GSSAPI/SPNEGO as security layer which is okay. I just
can't tell for sure if all communication is secured :-/
And still the kerberos/ldap solution seems to be a much cleaner way to
go. If it just worked... :)
--
Roman Sommer
"The value of an idea lies in the using of it." (Thomas Edison)
2005/11/5, Richard Bos
Op maandag 31 oktober 2005 12:23, schreef Roman Sommer:
might anyone please help?
This http://sadms.sourceforge.net was just announced on freshmeat...
SADMS takes care of handling configuration to achieve the integration of Linux hosts to an Active Directory domain, to the effect that:: Linux hosts become Windows domain hosts (and act either as station or server) Windows domain users become Linux users (authentication is offloaded to the domain
But suse is not supported.
-- Richard Bos Without a home the journey is endless