security = ads - Not working ....

[C.Lee Taylor]

>
>
>>    I seem to have a problem with security = ads, in my logs I get ...
>>
>>[2003/10/14 13:37:07, 1] libsmb/smb_signing.c:signing_good(227)
>>  signing_good: SMB signature check failed on seq 1!
>>[2003/10/14 13:37:07, 0] libsmb/clientgen.c:cli_receive_smb(121)
>>  SMB Signature verification failed on incoming packet!
>>[2003/10/14 13:37:07, 1] libsmb/smb_signing.c:signing_good(227)
>>  signing_good: SMB signature check failed on seq 1!
>>[2003/10/14 13:37:07, 0] libsmb/clientgen.c:cli_receive_smb(121)
>>  SMB Signature verification failed on incoming packet!
>>[2003/10/14 13:37:07, 1] libsmb/smb_signing.c:signing_good(227)
>>  signing_good: SMB signature check failed on seq 1!
>>[2003/10/14 13:37:07, 0] libsmb/clientgen.c:cli_receive_smb(121)
>>  SMB Signature verification failed on incoming packet!
>>    
>>
>
>Initial signing is failing. Are you sure you're talking to
>a signing enabled server ?
>
    Yes, Win2K3, but I was reading thru the mail list, and found that 
you need krb5 1.3.1 to get this working, so, first suggestion, maybe put 
a meesage in the debug that states one will need 1.3.1, or test to see 
if krb5 libs are not 1.3.1 and then put the message up.

    Second, if I upgrade my krb5 libs, do I need to recompile samba to 
take advantage of the need encodings, or does it find them at runtime? 
 The reason I ask, is if I do an upgrade of my RedHat system for test 
purpose, I have to upgrade quite alot, because RedHat does not package a 
libcom_err into krb5 lib, because e2fsprogs does this ... put alot of 
packages expect this lib ... so for a test, I will have to upgrade quite 
alot ...

Mailed
Lee