search for: mvxattr

...tatalk" (default). Instead of the correct org.netatalk.Metadata it used netatalk.Metadata Starting with Samba 4.6 vfs_fruit will use the correct "org.netatalk.Metadata" which means existing installations must rename this xattrs. For this purpose Samba now includes a new tool `mvxattr`. See below for further details. NEW FEATURES/CHANGES ==================== Kerberos client encryption types -------------------------------- Some parts of Samba (most notably winbindd) perform Kerberos client operations based on a Samba-generated krb5.conf file. A new parameter, "kerberos e...

...tatalk" (default). Instead of the correct org.netatalk.Metadata it used netatalk.Metadata Starting with Samba 4.6 vfs_fruit will use the correct "org.netatalk.Metadata" which means existing installations must rename this xattrs. For this purpose Samba now includes a new tool `mvxattr`. See below for further details. NEW FEATURES/CHANGES ==================== Kerberos client encryption types -------------------------------- Some parts of Samba (most notably winbindd) perform Kerberos client operations based on a Samba-generated krb5.conf file. A new parameter, "kerberos e...

...tatalk" (default). Instead of the correct org.netatalk.Metadata it used netatalk.Metadata Starting with Samba 4.6 vfs_fruit will use the correct "org.netatalk.Metadata" which means existing installations must rename this xattrs. For this purpose Samba now includes a new tool `mvxattr`. See below for further details. NEW FEATURES/CHANGES ==================== Kerberos client encryption types -------------------------------- Some parts of Samba (most notably winbindd) perform Kerberos client operations based on a Samba-generated krb5.conf file. A new parameter, "kerberos e...

...tatalk" (default). Instead of the correct org.netatalk.Metadata it used netatalk.Metadata Starting with Samba 4.6 vfs_fruit will use the correct "org.netatalk.Metadata" which means existing installations must rename this xattrs. For this purpose Samba now includes a new tool `mvxattr`. See below for further details. NEW FEATURES/CHANGES ==================== Kerberos client encryption types -------------------------------- Some parts of Samba (most notably winbindd) perform Kerberos client operations based on a Samba-generated krb5.conf file. A new parameter, "kerberos e...

...org.netatalk.Metadata > > it used > > netatalk.Metadata > > Starting with Samba 4.6 vfs_fruit will use the correct > "org.netatalk.Metadata" > which means existing installations must rename this xattrs. For this > purpose > Samba now includes a new tool `mvxattr`. See below for further details. > > > NEW FEATURES/CHANGES > ==================== > > Kerberos client encryption types > -------------------------------- > Some parts of Samba (most notably winbindd) perform Kerberos client > operations based on a Samba-generated krb5...

...will go into samba-ad-client samba_dnsupdate, samba_spnupdate - should these go to samba-ad-client? samba_upgradedns - samba-ad-client or samba-ad-dc? Or is it used at all outside of selftests and testprogs? Other files in there: profiles dumpmscat mvxattr oLschema2ldif pdbedit sharesec smbcontrol - this one should probably be moved to samba-common-bin (it can control winbindd too) This package used to depend on python ==================== winbind - winbindd, wbinfo and ntlm_auth ====================...