Hm, since samba would create AND use its own local UID's to manage privileges you could get access to files which you couldn't read if winbind would be started before samba ... Yes we have tested it ...
Wer das Kapital wählt wird durch das Kapital regiert! Who elects the capital, is governed by the capital! H CUH Rainer Peter Feller H On Fri, Jan 9, 2009 at 6:38 PM, Jamie Strandboge <[email protected]> wrote: > Thanks for taking the time to report this bug and helping to make Ubuntu > better. We appreciate the difficulties you are facing, but this appears > to be a "regular" (non-security) bug. I have unmarked it as a security > issue since this bug does not show evidence of allowing attackers to > cross privilege boundaries nor directly cause loss of data/privacy. > Please feel free to report any other bugs you may find. > > ** Visibility changed to: Public > > ** This bug is no longer flagged as a security issue > > -- > winbind is not started before samba, but should > https://bugs.launchpad.net/bugs/315427 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Ubuntu: New > > Bug description: > Hi, > in ubuntu 8.10 server (possibly other) > winbind should be started before samba is running > with same S20... winbind is started AFTER samba so resolving user/groups can > be messed up. > cups should also be clearly started before samba > so please increase the startup number of samba ... > Thanks > Rainer Peter Feller > may be this could be exploited ... > -- winbind is not started before samba, but should https://bugs.launchpad.net/bugs/315427 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
