search for: winbindf

...oups ?) would be trivial. > > It would be interesting to know whether you see the issue with settings > of winbind max domain connections higher then the default of 1. If so, > does increasing it to some sane value eg 10 help? > > -slow > > Well, looks like setting 'winbindf max domain connections' to a value above 1 makes 'wbinfo -u' no longer a threat, but it is pretty much ignored if 'winbind offline logon' is enabled... Can anyone explain why? Because when auth can be broken so easily--just run 'wbinfo -u', for which you don't even n...

...would be interesting to know whether you see the issue with settings > > of winbind max domain connections higher then the default of 1. If so, > > does increasing it to some sane value eg 10 help? > > > > -slow > > > > > > Well, looks like setting 'winbindf max domain connections' to a value above 1 makes 'wbinfo -u' > no longer a threat, but it is pretty much ignored if 'winbind offline logon' is enabled... > Can anyone explain why? Because when auth can be broken so easily--just run 'wbinfo -u', > for which you d...

...see the issue with settings > > > of winbind max domain connections higher then the default of 1. If so, > > > does increasing it to some sane value eg 10 help? > > > > > > -slow > > > > > > > > > > Well, looks like setting 'winbindf max domain connections' to a value above 1 makes 'wbinfo -u' > > no longer a threat, but it is pretty much ignored if 'winbind offline logon' is enabled... > > Can anyone explain why? Because when auth can be broken so easily--just run 'wbinfo -u', > >...

Hi, Recently I by mistake ran `wbinfo -u <username>` when I was actually intending to run `wbinfo -n <username>`. It ignored the <username> part and proceeded to fetch the usernames. On a small domain this shouldn't be too much of an issue, but I did it on a domain with thousands upon thousands of users. The result was that Winbind became for all intents and purposes