"Paul Hampson" <[EMAIL PROTECTED]> wrote: > And the modules/rlm_smb file supplies two extra functions... Maybe > modules/rlm_smb should be calling the code in libradius?
Yes. > Hmm. rlm_mschap and rlm_eap_leap use lib/smbdes.c... And > rlm_x99_token may do, as well. > > Blah! This is GPL, and in libradius. :-( (Did I mention that > earlier, or was it a different file...?) I think it was the same file. > If I get around to making mcrypt work, maybe I should rewrite > smbdes.c to using that instead of the samba routines? I would prefer not. mcrypt is installed on few (if any) machines. smbdes licensing issues can be resolved more easily than convincing umpteen people to install mcrypt. > I'll leave rlm_smb alone for the moment, though. If anyone's > up to it, patching this to libsmb from Samba would be a > "fun" exercise... Resynching to pam_smb would be easier. Absolutely. I took a look at implementing rlm_smb via libsmb, and decided that there was nothing I could do to perform "username/password" authentication. Instead, it would need Samba configuration files, and huge amounts of other things I couldn't figure out. Copying pam_smb and editing it was much simpler. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
