Bug#999876: samba: winbind fails to start with `allow trusted domains: no`

2021-11-17 Thread John Kristensen
Package: samba
Version: 2:4.13.13+dfsg-1~deb11u2
Severity: important
Tags: upstream

Dear Maintainer,

When setting `allow trusted domains: no` in `/etc/samba/smb.conf` the winbind
service fails to start with the following error:

[2021/11/17 19:07:33.137859,  0] 
../../source3/winbindd/winbindd_cache.c:3203(initialize_winbindd_cache)
  initialize_winbindd_cache: clearing cache and re-creating with version 
number 2
[2021/11/17 19:07:33.140746,  0] 
../../source3/winbindd/winbindd_util.c:1140(init_domain_list)
  init_domain_list: add_trusted_domain BUILTIN returned 
NT_STATUS_NO_SUCH_DOMAIN
[2021/11/17 19:07:33.142209,  0] 
../../source3/winbindd/winbindd.c:1458(winbindd_register_handlers)
  unable to initialize domain list

Setting the default value of `allow trusted domains: yes` allows winbind to
start without any problems.

This seems to be a know upstream bug[1] and there is a one-line patch to
fix the problem[2].

Thanks,
John.

[1] https://bugzilla.samba.org/show_bug.cgi?id=14899
[2] https://gitlab.com/samba-team/samba/-/merge_requests/2246/diffs


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

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

Kernel: Linux 5.10.0-8-amd64 (SMP w/1 CPU thread)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages samba depends on:
ii  adduser  3.118
ii  dpkg 1.20.9
ii  init-system-helpers  1.60
ii  libbsd0  0.11.3-1
ii  libc62.31-13
ii  libgnutls30  3.7.1-5
ii  libldb2  2:2.2.3-2~deb11u1
ii  libpam-modules   1.4.0-9
ii  libpam-runtime   1.4.0-9
ii  libpopt0 1.18-2
ii  libpython3.9 3.9.2-1
ii  libtalloc2   2.3.1-2+b1
ii  libtasn1-6   4.16.0-2
ii  libtdb1  1.4.3-1+b1
ii  libtevent0   0.10.2-1
ii  libwbclient0 2:4.13.13+dfsg-1~deb11u2
ii  lsb-base 11.1.0
ii  procps   2:3.3.17-5
ii  python3  3.9.2-3
ii  python3-dnspython2.0.0-1
ii  python3-samba2:4.13.13+dfsg-1~deb11u2
ii  samba-common 2:4.13.13+dfsg-1~deb11u2
ii  samba-common-bin 2:4.13.13+dfsg-1~deb11u2
ii  samba-libs   2:4.13.13+dfsg-1~deb11u2
ii  tdb-tools1.4.3-1+b1

Versions of packages samba recommends:
ii  attr1:2.4.48-6
ii  logrotate   3.18.0-2
ii  python3-markdown3.3.4-1
ii  samba-dsdb-modules  2:4.13.13+dfsg-1~deb11u2
ii  samba-vfs-modules   2:4.13.13+dfsg-1~deb11u2

Versions of packages samba suggests:
pn  bind9  
pn  bind9utils 
pn  ctdb   
pn  ldb-tools  
pn  ntp | chrony   
pn  smbldap-tools  
pn  ufw
ii  winbind2:4.13.13+dfsg-1~deb11u2

-- no debconf information



Bug#754248: python-virtualenv: Error when attempting to create a python2.6 virtualenv

2015-01-07 Thread John Kristensen
On 19/11/14 08:17, Stefano Rivera wrote:
> Hi Renat (2014.08.06_05:27:47_-0700)
>> I tried to replace {} with % operator and now I'm having following errors:
> 
>> ImportError: cannot import name CertificateError
> 
> That is being tracked in #755106 and #763389, and I intend to fix it
> soon.
> 
> SR
> 

With #755106 and #763389 resolved the attached patch now fixes this
issue for me.
Index: python-virtualenv-1.11.6+ds-1/debian/patches/use-wheels.patch
===
--- python-virtualenv-1.11.6+ds-1/debian/patches/use-wheels.patch
+++ python-virtualenv-1.11.6+ds-1/debian/patches/use-wheels.patch
@@ -89,9 +89,9 @@
 +if error.errno != errno.EEXIST:
 +raise
 +for project in DEBIAN_WHEEL_DEPS:
 +wheel_names = glob.glob(
++'/usr/share/python-wheels/{0}-*.whl'.format(project))
-+'/usr/share/python-wheels/{}-*.whl'.format(project))
 +if len(wheel_names) == 0:
 +raise RuntimeError('missing dependency wheel %s' % project)
 +assert len(wheel_names) == 1, wheel_names
 +wheel_name = os.path.basename(wheel_names[0])


Bug#754248: python-virtualenv: Error when attempting to create a python2.6 virtualenv

2014-07-08 Thread John Kristensen
Package: python-virtualenv
Version: 1.11.6-2
Severity: important

Dear Maintainer,

Attempting to create a python2.6 virtualenv using the following command:

  virtualenv -p python2.6 venv

Results in the follow error:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/virtualenv.py", line 2378, in 
main()
  File "/usr/lib/python3/dist-packages/virtualenv.py", line 830, in main
symlink=options.symlink)
  File "/usr/lib/python3/dist-packages/virtualenv.py", line 1016, in
create_environment
'/usr/share/python-wheels/{}-*.whl'.format(project))
ValueError: zero length field name in format

It seems to be due to the use of '{}' for string substitution which is not
compatible with python2.6.



-- System Information:
Debian Release: jessie/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (460, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-virtualenv depends on:
ii  python 2.7.6-2
ii  python-pip-whl 1.5.6-2
ii  python-pkg-resources   5.3-1
ii  python-setuptools-whl  5.3-1

Versions of packages python-virtualenv recommends:
ii  virtualenv  1.11.6-2

python-virtualenv suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#735372: docker.io: errors with bash completion

2014-01-14 Thread John Kristensen
Package: docker.io
Version: 0.6.7+dfsg1-3
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Issue occurs after installing docker.io without making any other changes.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Type the following at the command prompt:

  $ docker.io run 

   * What was the outcome of this action?

The follow was output to the console:

  $ docker.io run bash: docker: command not found
  bash: docker: command not found

   * What outcome did you expect instead?

No errors


A temporary workaround seems be to create an alias 'docker=docker.io'



-- System Information:
Debian Release: jessie/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (460, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages docker.io depends on:
ii  adduser  3.113+nmu3
ii  aufs-tools   1:3.2+20130722-1.1
ii  init-system-helpers  1.14
ii  iptables 1.4.21-1
ii  libc62.17-97
ii  libsqlite3-0 3.8.2-1
ii  lxc  0.9.0~alpha3-2+deb8u1

Versions of packages docker.io recommends:
ii  ca-certificates  20130906

docker.io suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#689008: msktutil fails when using --verbose

2012-09-28 Thread John Kristensen
Package: msktutil
Version: 0.4.1-4
Severity: normal


msktutil fails when using "--verbose":
root@:~# msktutil --create --computer-name  --server 
 --user-creds-only --verbose
 -- init_password: Wiping the computer password structure
 -- get_default_keytab: Obtaining the default keytab name: 
FILE:/etc/krb5.keytab
 -- create_fake_krb5_conf: Created a fake krb5.conf file: 
/tmp/.msktkrb5.conf-sED9sN
 -- reload: Reloading Kerberos Context
 -- finalize_exec: SAM Account Name is: $
 -- try_user_creds: Checking if default ticket cache has tickets...
 -- finalize_exec: Authenticated using method 4

 -- ldap_connect: Connecting to LDAP server:  try_tls=YES
 -- ldap_connect: Connecting to LDAP server:  try_tls=NO
SASL/GSSAPI authentication started
SASL username: @
SASL SSF: 56
SASL data security layer installed.
 -- ldap_connect: LDAP_OPT_X_SASL_SSF=56

Error: ldap_connect failed
--> Is your kerberos ticket expired? You might try re-"kinit"ing.
 -- ~KRB5Context: Destroying Kerberos Context


but works find if "--verbose" is left out:
root@:~# msktutil --create --computer-name  --server 
 --user-creds-only
No computer account for  found, creating a new one.
dn: cn=,CN=Computers,DC=



-- System Information:
Debian Release: 6.0.5
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages msktutil depends on:
ii  libc6   2.11.3-3 Embedded GNU C Library: Shared lib
ii  libcomerr2  1.41.12-4stable1 common error description library
ii  libgcc1 1:4.4.5-8GCC support library
ii  libk5crypto31.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - C
ii  libkrb5-3   1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries
ii  libldap-2.4-2   2.4.23-7.2   OpenLDAP libraries
ii  libsasl2-modules-gs 2.1.23.dfsg1-7   Cyrus SASL - pluggable authenticat
ii  libstdc++6  4.4.5-8  The GNU Standard C++ Library v3

msktutil recommends no packages.

msktutil suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org