[Samba] SambaPosix tool
debian at lhanke.de
Thu Nov 6 04:15:14 MST 2014
Am 05.11.2014 um 23:18 schrieb Rowland Penny:
> On 05/11/14 22:07, Lars Hanke wrote:
>> Am 05.11.2014 um 22:31 schrieb Rowland Penny:
>>> On 05/11/14 21:17, Lars Hanke wrote:
>>>> As announced several weeks ago, I'd share my tool to manage POSIX
>>>> attributes in Samba4 AD LDAP.
>>>> You can find it at https://github.com/laotse/SambaPosix.
>>>> It works on my particular system, but it is largely untested and
>>>> weakly documented. But it supports a --dry-run mode, which produces
>>>> LDIF, if you don't trust the tool. ;)
>>>> I'll welcome contributions: tests, documentation, comments,
>>>> extensions, fixes, ...
>>>> Have fun,
>>>> - lars.
>>> After a quick scan, it would appear that you are adding 'posixAccount'
>>> to a user, please don't do this, ADUC doesn't do this because the
>>> 'posix*' objectClasses are auxiliaries of other objectClasses, like
>> In a LDAP with schema these would even be required. I accept that M$
>> doesn't do it, so it might call for another option.
>> In my particular setup, I did not posixify all users and groups. E.g.
>> Administrator is no POSIX user. Having the object classes around helps
>> to filter out these, so nslcd and friends don't have to bother with
>> incomplete RFC fields. This is to say, I see a benefit in having the
>> objectClasses. So far I did not encounter problems. Is there any
>> trouble known?
>> - lars.
> OK, I see where you are coming from, but what if you come up with
> something that requires these objectClasses, but somebody then decides
> to add a large group of users with ADUC (these will not have the posix
> objectClasses), these users will not show up in whatever it is that you
> are using that requires the posix objectClasses. I personally think that
> it is better to only rely on objectClasses & attributes that ADUC would
> add, that way you can never have problems caused by the posix
> objectClasses being there or not.
> What you have to remember is, you are now dealing with AD not LDAP.
I pondered on that last night. Someone using ADUC probably uses a
different profile on the libnss-ldap* end. E.g. ADUC puts the POSIX user
name in 'msSFU30Name'. It may be an idea to add profile options to the
tool, including profiles for ADUC compatibility. But I'll have to
further explore ADUC to detail what that might be.
On the other hand admins using a Linux console and those using ADUC
probably have a small cross-section. The profile option will help
infrastructures with admins of both sorts.
My environments are Linux centered. Most Windozers are VM. Windows is
only used to run specialized software not available under Linux. So I
would sacrifice ADUC compatibility for benefits on the POSIX side. The
core benefit of AD, i.e. cross-platform SSO, must however be maintained.
I never used the M$ POSIX integration stuff (is there anything beyond
NFS?), but I accept that we should not break that.
More information about the samba