search for: slice_size

..., you can be compatible using idmap_rid if you set a low range identical to that of the low range in SSSD. SSSD determines low range for initial id slice using approximately the following algorithm IIRC: ``` uint32_t hash_val = 0; int our_slice = 0; int max_slices = 10000; int final_value = 0; int slice_size = 20000 hash_val = murmur3(sid_str, strlen(sid_str), 0xdeadbeef); our_slice = hash_val % max_slices; final_value = our_slice * slice_size +slice_size; ``` This works for the first slice, but slices after that are non-deterministic.

...tested sssd-winbind-idmap yet I mentioned in another response > > SSSD determines low range for initial id slice using approximately the > following algorithm IIRC: > ``` > uint32_t hash_val = 0; > int our_slice = 0; > int max_slices = 10000; > int final_value = 0; > int slice_size = 20000 > > hash_val = murmur3(sid_str, strlen(sid_str), 0xdeadbeef); > our_slice = hash_val % max_slices; > final_value = our_slice * slice_size +slice_size; > ``` > This works for the first slice, but slices after that are non-deterministic. >

...t a low range identical to that of the low range > in SSSD. > > SSSD determines low range for initial id slice using approximately the > following algorithm IIRC: > ``` > uint32_t hash_val = 0; > int our_slice = 0; > int max_slices = 10000; > int final_value = 0; > int slice_size = 20000 > > hash_val = murmur3(sid_str, strlen(sid_str), 0xdeadbeef); > our_slice = hash_val % max_slices; > final_value = our_slice * slice_size +slice_size; > ``` > This works for the first slice, but slices after that are > non-deterministic. >

As it turns out, with the proprietary firmware, the VP3 and VP4 interfaces are identical. Furthermore, this is all already implemented for nvc0. So these patches (a) move the easily sharable bits of the nvc0 implementation into the nouveau directory, and then (b) implement the other parts in nv50. The non-shared parts are still largely copies, but there are some differences, not the least of which

On Thu, Sep 03, 2020 at 06:43:32PM +0100, Rowland penny via samba wrote: > On 03/09/2020 18:04, Johan Hattne via samba wrote: > > Dear all; > > > > Would anybody be able to tell me what the idmap configuration is to have > > Samba do the same SID-to-user/group mapping as the SSSD defaults?? I was > > convinced I saw it on this list or the wiki not too long ago,

On 03/09/2020 20:01, Andrew Walker wrote: > Whoops, fumbled my response a bit. slice size by default is 200,000, > and to clarify the SID passed into murmur3() is the domain SID, not > SID?of individual user. Though, manpage for sssd-ad should be > consulted for precise details. My understanding though is as long as > everything fits in one slice, then you can just use RID. If

...first_rid))) { id = range_params->min_id + (rid - range_params->first_rid); if (id <= range_params->max_id) { *_id = id; return true; } } return false; } ``` So pretty easy fit with idmap_rid if the domain's highest RID is < slice_size in SSSD. So it might be helpful for people to at least try "id DOMAIN\\administrator" on Linux client with SSSD joined to a Windows AD domain (assuming that this is an issue of trying to make sure that clients with SSSD and Winbind end up with similar ID mapping), subtract 500 from from t...