Your message dated Sat, 8 Oct 2022 01:16:00 +0300
with message-id <[email protected]>
and subject line Re: Bug#1011269: winbind: Winbind does not start when "allow 
trusted domain" is set to "no"
has caused the Debian Bug report #1011269,
regarding winbind: Winbind does not start when "allow trusted domain" is set to 
"no"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1011269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011269
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: winbind
Version: 2:4.13.13+dfsg-1~deb11u3
Severity: normal

Dear Maintainer,

After upgrading from Debian Buster to Debian Bullseye winbind does not start 
anymore
because we have "allow trusted domain" set to "no" in smb.conf.

winbind exits immediately with:

init_domain_list: add_trusted_domain BUILTIN returned NT_STATUS_NO_SUCH_DOMAIN

This is (fixed) Samba bug https://bugzilla.samba.org/show_bug.cgi?id=14899

As a workaround we can set "allow trusted domain" to "yes" but like to avoid 
this
as we have a very large forest with many domains all over the world creating 
delays 
in resolving users & groups.

Is there a chance this can be considered a regression and the fix applied in 
the next Debian stable point release?

Thanks,
Geert

-- Package-specific info:
* /etc/samba/smb.conf present, but not attached
* /var/lib/samba/dhcp.conf not present

-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-14-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages winbind depends on:
ii  init-system-helpers  1.60
ii  libbsd0              0.11.3-1
ii  libc6                2.31-13+deb11u3
ii  libgnutls30          3.7.1-5
ii  libldap-2.4-2        2.4.57+dfsg-3
ii  libpopt0             1.18-2
ii  libtalloc2           2.3.1-2+b1
ii  libtdb1              1.4.3-1+b1
ii  libtevent0           0.10.2-1
ii  libwbclient0         2:4.13.13+dfsg-1~deb11u3
ii  lsb-base             11.1.0
ii  samba-common         2:4.13.13+dfsg-1~deb11u3
ii  samba-common-bin     2:4.13.13+dfsg-1~deb11u3
ii  samba-libs           2:4.13.13+dfsg-1~deb11u3

winbind recommends no packages.

Versions of packages winbind suggests:
ii  libnss-winbind  2:4.13.13+dfsg-1~deb11u3
ii  libpam-winbind  2:4.13.13+dfsg-1~deb11u3

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 2:4.13.13+dfsg-1~deb11u4

On Thu, 19 May 2022 14:14:16 +0300 Michael Tokarev <[email protected]> wrote:
...
This is fixed in 2:4.13.13+dfsg-1~deb11u4 which is waiting for the
review and acceptance of the release team since Apr-15, see #1009726.

Hopefully I wont forget to mark this one as fixed when samba is accepted.

..which I did. Closing this bugreport now.

/mjt

--- End Message ---

Reply via email to