Debian etch samba update

Then restart the dist-upgrade process again. If you have only the default packages installed the upgrade process should now finish without raising more errors. Problem upgrading bind The only remaining upgrade issue is that the user of bind9 has changed, so you'll have to chown all bind-configuration files. Samba groupmaps handeling changed There has been a change in how samba handles groupmaps between sarge and etch. Samba in sarge handled groupmaps internally, so a unix group was also a samba group.

In etch samba keeps groupmap information in the LDAP database. Unfortunatly this issue was discovered too late for our LDAP admin tool "lwat" to be aware of the situation. When you upgrade your LDAP from a sarge installation, you must make sure to create the Domain Admins account, neccessary for correct samba domain operation.

Upgrade to the sarge based version first, a howto can be found at? Then upgrade to Terrra etch-based Release. Wiki Login. Message 45 received at bugs. Thu, 19 May GMT full text , mbox , link.

Message 53 received at bugs. Bug reassigned from package ' winbind ' to ' libkrb '. Bug reassigned from package ' libkrb ' to ' krb5 '. Fri, 20 May GMT full text , mbox , link. Bug reassigned from package ' krb5 ' to ' libgssapi-krb '. Forcibly Merged Bug archived. Wed, 06 Jul GMT full text , mbox , link. Send a report that this bug log contains spam. From: "Alexander R. Odd: Wrote some comments, click on comments in edit bar to toggle comments visibility.

The modifications where done on a convert from dbsam to ldap by pdbedit -i tdbsam -e ldapsam. I'm not sure this is a valid method, it seems that pdbedit fill in the default value where an attribute is not defined. Only the attributes not found on Edu Etch are listed: The comments in the table represent the attribute description as appears in The Official Samba 3.

If this attribute is omitted, then the account will never expire. Using this attribute together with shadowExpire of the shadowAccount ObjectClass will enable accounts to expire completely on an exact date. If this attribute is not set, the user will be free to change his password whenever he wants.

If this value is set to 0, the user will have to change his password at first login. If this attribute is not set, then the password will never expire. To supplement this information I searched the release notes of Samba for the attributes mentioned here. Since Samba 3. In any case the nessesary measures to secure this attribute in slapd.