[XAD] Re: Security Identifier (SID) to User Identifier (uid) ResolutionSystem

[Nicolas Williams]

On Wed, Dec 29, 1999 at 12:24:49PM +1100, Luke Howard wrote:
> 
> I had always thought an algorithmic mapping between NT and UNIX
> identifiers was the Way To Go from an administrative perspective
> until I spoke to people who managed existing deployments, where
> uids and SIDs had already been allocated. At least with a single
> directory, you can put the identifiers in the same place.
> 
> That said, I still believe an algorithmic mapping is a good
> idea for deployments that want it (for example, deployments with
> a minimal UNIX infrastructure, or a minimal NT one). The mapping
> logic could be in a number of places: in SAMBA, in an NSS module
> for UNIX, or in the directory server itself.

Yes, yes. Though you can't currently put the mapping logic into an NSS
module as there is no standard get*by*() API that involves SIDs (you can
make reference to SIDs internally, but you can't have those functions
take a SID as an argument or return SID information).

The directory is a good place to put either or both express mappings and
logical mappings. This is why Samba could use a little API so others can
provide it with modules to make these lookups via a directory.

Still, the uid/gid->local SID mapping Samba fileservers implement now is
not bad. There is no urgency to implement such an API. Though I bet Luke
would rush to it if given the go ahead :)

> -- Luke
> 

Nico

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.