I notices some objectclass violations in wireshark which are cause by missing attributes in the netscape schema file: bjacke@pell:~/SVN/master> grep 1.3.6.1.4.1.7165.2.1.5 ./examples/LDAP/samba-schema-netscapeds5.x attributeTypes: ( 1.3.6.1.4.1.7165.2.1.54 NAME 'sambaPasswordHistory' DESC 'Concatenated MD4 hashes of the unicode passwords used on this account' EQUALITY caseIgnoreIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26{32} ) attributeTypes: ( 1.3.6.1.4.1.7165.2.1.55 NAME 'sambaLogonHours' DESC 'Logon Hours' EQUALITY caseIgnoreIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26{42} SINGLE-VALUE ) bjacke@pell:~/SVN/master> grep 1.3.6.1.4.1.7165.2.1.5 ./examples/LDAP/samba.schema #attributetype ( 1.3.6.1.4.1.7165.2.1.5 NAME 'logonTime' attributetype ( 1.3.6.1.4.1.7165.2.1.55 NAME 'sambaLogonHours' attributetype ( 1.3.6.1.4.1.7165.2.1.54 NAME 'sambaPasswordHistory' attributetype ( 1.3.6.1.4.1.7165.2.1.51 NAME 'sambaSIDList' ##attributetype ( 1.3.6.1.4.1.7165.2.1.50 NAME 'sambaPrivName' ##attributetype ( 1.3.6.1.4.1.7165.2.1.52 NAME 'sambaPrivilegeList' attributetype ( 1.3.6.1.4.1.7165.2.1.53 NAME 'sambaTrustFlags' attributetype ( 1.3.6.1.4.1.7165.2.1.58 NAME 'sambaMinPwdLength' attributetype ( 1.3.6.1.4.1.7165.2.1.59 NAME 'sambaPwdHistoryLength' the missing attributes have been missing at least since Samba 3.2.
the FDS schema file works fine with the netscape/sun DS and that one is uptodate. We should remove the bogous samba-schema-netscapeds5.x and place a samba-schema-netscapeds5.x.README there instead pointing to the FDS schema file. Any objections?
b31f773ae1640313dc1ba86b334e9bbb9cb31bd6 in master contains the replacement of the ancient schema file with a README file. Karo, can you pick this to 3.6, 3.5, 3.4, 3.3 and 3.2? It's up to you if you inlcude the older of the mentioned branches ...
Re-assigning to Günther for review.
Yes, that looks fine.
Pushed to v3-6-test and v3-5-test. Closing out bug report. Thanks!