RFC: Draft 2 of passdb redesign

[Anders C. Thorsen]

With a large possibility of sounding stupid:

since the passdb should not have the knowledge of UID/GIDs,
for mapping purporses. Would it then be an idea of having 
alias/mapping support, so that one could have a smoother
way of managing it in systems like LDAP, etc?

SAM_ACCOUNT* could then contain a different username (unix name)
than the one provided to pdb_getsampwnam. Am I right?

--Anders

On Fri, Nov 10, 2000 at 12:01:37PM -0600, Gerald Carter wrote:
> Gerald Carter wrote:
> > 
> >    /*
> >       Search Functions :
> > 
> >       Each function returns a pointer to a static area
> >       of memory (one for all functions, not one for each
> >       function).  This is done for effenciency.  If the
> >       caller wishes to maintain a copy of the SAM_ACCOUNT
> >       struct across calls(), it must make of copy of the
> >       struct returned.
> >    */
> >    SAM_ACCOUNT* pdb_getsampwent ();
> >    SAM_ACCOUNT* pdb_getsampwnam (char* username);
> >    SAM_ACCOUNT* pdb_getsampwuid (uid_t uid);
> >    SAM_ACCOUNT* pdb_getsampwrid (uint32 rid);
> 
> 
> Add 
> 
> 	void* pdb_setsampwent();
> 	void  pdb_endsampwent();
> 
> for enumeration purposes.
> 
> 
> 
> 
> Cheers, jerry
> ----------------------------------------------------------------------
>    /\  Gerald (Jerry) Carter                     Professional Services
>  \/    http://www.valinux.com/  VA Linux Systems   gcarter at valinux.com
>        http://www.samba.org/       SAMBA Team          jerry at samba.org
>        http://www.plainjoe.org/                     jerry at plainjoe.org
> 
>        "...a hundred billion castaways looking for a home."
>                                 - Sting "Message in a Bottle" ( 1979 )