search for: _nss_

...ld be independent from any domain (i.e. the share should be accessable via windows client) to come around the useraccount-restriction (as samba is getting information via getpwnam_r()) i think a nss module for database 'passwd' is necessary. i am starting to think that my implementation of _nss_<sourcename>_getpwnam_r() is wrong nevertheless, if you can think of any other solution without the need of interfacing with getpwnam - plz let me know! thx hari On Mon, Jan 21, 2019 at 10:37 AM Rowland Penny via samba < samba at lists.samba.org> wrote: > On Mon, 21 Jan 2019 09:3...

On Mon, 21 Jan 2019 12:54:00 -0400 Robert Marcano via samba <samba at lists.samba.org> wrote: > On 1/21/19 11:04 AM, Rowland Penny via samba wrote: > > On Mon, 21 Jan 2019 10:43:35 -0400 > > Robert Marcano via samba <samba at lists.samba.org> wrote: > > > >> On 1/21/19 10:24 AM, Harald Glanzer via samba wrote: > >>> hello & thx for your

...tegies. I am pretty sure it should work for standalone servers. > > to come around the useraccount-restriction (as samba is getting information > via getpwnam_r()) i think a nss module for database 'passwd' is necessary. > i am starting to think that my implementation of > _nss_<sourcename>_getpwnam_r() is wrong > > nevertheless, if you can think of any other solution without the need of > interfacing with getpwnam - plz let me know! > > thx > hari > > > On Mon, Jan 21, 2019 at 10:37 AM Rowland Penny via samba < > samba at lists.s...

thats interesting. shouldn't samba force to authenticate every distinct username, accessing different shares? as written, if i want to access directory /data/samba/username_a, i need to supply the correct password for username_a, as hashed in smbpasswd. smb.conf: -------- 8< ------- ... valid users = %S path = /data/samba/%S ... -------- 8< ------- if in the next step i want to access