similar to: Prevent `wbinfo -u` from making Winbind unresponsive

On Wed, Apr 01, 2020 at 03:33:00PM -0700, Jeremy Allison via samba wrote: > On Wed, Apr 01, 2020 at 02:09:57PM -0700, Alexey A Nikitin via samba wrote: > > 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

On Wed, Apr 01, 2020 at 02:09:57PM -0700, Alexey A Nikitin via samba wrote: > 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

On Friday, 3 April 2020 10:46:54 PDT Ralph Boehme wrote: > Am 4/1/20 um 11:09 PM schrieb Alexey A Nikitin via samba: > > Is there a way, preferrably without ugly hacks, to prevent this from happening on accident, by mistake? By this I mean ideally so that Winbind remains responsive even if someone mistakenly ran `wbinfo -u` or `wbinfo -g`, but limiting the result sets of these commands or

On Fri, Apr 03, 2020 at 07:46:54PM +0200, Ralph Boehme via samba wrote: > Am 4/1/20 um 11:09 PM schrieb Alexey A Nikitin via samba: > > Is there a way, preferrably without ugly hacks, to prevent this from happening on accident, by mistake? By this I mean ideally so that Winbind remains responsive even if someone mistakenly ran `wbinfo -u` or `wbinfo -g`, but limiting the result sets of

On Fri, Apr 10, 2020 at 02:37:45PM -0700, Jeremy Allison via samba wrote: > On Fri, Apr 03, 2020 at 03:26:42PM -0700, Alexey A Nikitin via samba wrote: > > On Friday, 3 April 2020 10:46:54 PDT Ralph Boehme wrote: > > > Am 4/1/20 um 11:09 PM schrieb Alexey A Nikitin via samba: > > > > Is there a way, preferrably without ugly hacks, to prevent this from happening on

Am 4/1/20 um 11:09 PM schrieb Alexey A Nikitin via samba: > Is there a way, preferrably without ugly hacks, to prevent this from happening on accident, by mistake? By this I mean ideally so that Winbind remains responsive even if someone mistakenly ran `wbinfo -u` or `wbinfo -g`, but limiting the result sets of these commands or blocking them altogether is acceptable too. well, blocking it

On Fri, Apr 03, 2020 at 03:26:42PM -0700, Alexey A Nikitin via samba wrote: > On Friday, 3 April 2020 10:46:54 PDT Ralph Boehme wrote: > > Am 4/1/20 um 11:09 PM schrieb Alexey A Nikitin via samba: > > > Is there a way, preferrably without ugly hacks, to prevent this from happening on accident, by mistake? By this I mean ideally so that Winbind remains responsive even if someone

On Fri, Apr 10, 2020 at 02:41:39PM -0700, Jeremy Allison wrote: > On Fri, Apr 10, 2020 at 02:37:45PM -0700, Jeremy Allison via samba wrote: > > On Fri, Apr 03, 2020 at 03:26:42PM -0700, Alexey A Nikitin via samba wrote: > > > no longer a threat, but it is pretty much ignored if 'winbind offline logon' is enabled... > > > Can anyone explain why? Because when auth

Hello group, I'm hitting a problem where group resolution through winbind seems to time out sometimes, which in turn causes invalid group information to propagate to Cronjob users or similar. The profiling information that winbind spits out is the following: [2019/08/22 14:34:14.809540, 0] ../source3/winbindd/winbindd.c:1058(winbind_client_processed) winbind_client_processed: request

On Wednesday, 27 May 2020 16:21:31 PDT Jeremy Allison wrote: > On Wed, May 27, 2020 at 12:54:49PM -0700, Alexey A Nikitin via samba wrote: > > 3. Are the rules for how a DC gets put into NEG_CONN_CACHE documented anywhere besides the code itself, or wading through the code is my only option of getting to know the criteria? > > Only in the code I think, added in: > >

On Mon, Oct 17, 2016 at 09:41:10AM -0700, Jeremy Allison via samba wrote: > On Mon, Oct 17, 2016 at 05:13:08PM +0100, Rebecca Gellman via samba wrote: > > > > > > Hi, > > > > So I did some digging into the source code, and I think I've found the > > issue. Around line 120 of source3/libads/cldap.c: > > > > for (i=0; i<num_servers;

On Friday, 18 October 2019 12:24:46 PDT Ralph Boehme wrote: > You won't loose connectivity anyway. winbindd will just have to go > through DC lookup again in certain scenarios. This is exactly what I'd like to avoid. As I wrote in another message in this thread, it appears that switching DC shortly after domain join causes machine authentication failures until the new machine

On Thursday, 13 June 2019 09:18:25 PDT Goetz, Patrick G via samba wrote: > On 6/13/19 10:48 AM, Alexey A Nikitin via samba wrote: > > According to the MS docs SID=('S-'+version+identifier authority value+domain or computer identifier+RID). The SIDs that don't contain RID are the special cases of Machine SID, Domain SID, Service SID, and some predefined universal well-known

On Thursday, 13 June 2019 00:41:09 PDT Rowland penny via samba wrote: > On 13/06/2019 07:55, Alexey A Nikitin wrote: > > On Wednesday, 12 June 2019 13:07:56 PDT Rowland penny via samba wrote: > >>>> I think you mean 'RID' instead of 'SID' > >>> Yes, you're right. The Windows people seem to use the terms synonymously. > >> I cannot

Sorry for not being accurate in the original question. My testing environment is set to 20ms frames (PCM 16 8 1 to be precise). I have verified that all the frames that I feed to the AEC have the fixed size of 320 bytes. So this is why I am presuming that the the dumped files should be of equal size. The output signal is good and not distorted. It has echo, though. In a try to diagnose that I

On Friday, 18 October 2019 10:52:40 PDT Rowland penny via samba wrote: > On 18/10/2019 18:26, Alexey A Nikitin via samba wrote: > > Hi everyone, > > > > I have few questions about Winbind on AD DS domain member I'm having difficulty finding answers to in the docs on my own: > > * does Winbind remember the last DC it was connected to on shutdown, will it attempt to

On Wednesday, 5 February 2020 13:11:27 PST Rowland penny via samba wrote: > No, sorry, but your client needs to have the same time as the DC (+/- 5 > mins), so if you haven't installed an NTP client, I suggest you do. Speaking of which, any suggestions on what's the best way to found out which NTP servers the client should be tuned to in AD DS? From what I understand, they are not

SSSD has auto_private_groups setting which effectively automatically creates a private user group when getting users from AD that either don't have gidNumber set for them or have gidNumber set to be the same as uidNumber. Is there any option in Winbind that could help achieve a similar result? Say, I have a user 'alexey' with uidNumber 1174235, when I run `id alexey` I want to get

On Tuesday, 5 November 2019 01:37:15 PST Rowland penny via samba wrote: > On 04/11/2019 18:52, Alexey A Nikitin wrote: > > On Sunday, 3 November 2019 01:41:18 PST Rowland penny via samba wrote: > >> As I said, you cannot use 'winbind use default domain = yes' with > >> 'autorid', it makes all users and groups members of the same domain, > >> this

We are running asteriskNow 1.4.18 and after a few days it becomes unresponsive and inbound INVITEs timeout. We just reboot the box to resolve it. But it seems to be occurring more regularly now. I am hesitant to move to latest version, but will do if needed. Any guidance or troubleshooting modes I may use will be helpful. -------------- next part -------------- An HTML attachment was