Bug#857759: (no subject)

2017-03-15 Thread Stijn Tintel
Hi again, looks like I made a mistake while reporting this bug. The version of mosquitto in Debian 8 does not have this bug, it was introduced later. However, the bug does exist in version 1.4.10-2 for Debian 9. Can this bug be updated, or do I need to report a new one? It would be very

Bug#857759: libmosquitto1 does not support connecting to IPv6 hosts with TLS enabled

2017-03-14 Thread Stijn Tintel
Package: libmosquitto1 Version: 1.3.4-2 Severity: important Dear Maintainer, This is a known issue that was fixed upstream. Please consider backporting https://github.com/eclipse/mosquitto/commit/98ea68490626b1d18aee2004b411294c85e62212 -- System Information: Debian Release: 8.7 APT prefers

Bug#814110: (no subject)

2016-11-03 Thread Stijn Tintel
Reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=186701

Bug#408093: closed by Bastian Blank (Re:Bug#408093: linux-image-2.6.18-3-xen-686: CONFIG_LEGACY_PTY_COUNT=16)

2007-01-24 Thread Stijn Tintel
Goswin von Brederlow wrote: Stijn Tintel [EMAIL PROTECTED] writes: Bastian The machine were I reported this problem from, is running Debian Etch + Xen. Everything is installed from packages from the Etch repository, no self-built packages, etc. Do you have devpts mounted? MfG

Bug#408093: closed by Bastian Blank (Re:Bug#408093: linux-image-2.6.18-3-xen-686: CONFIG_LEGACY_PTY_COUNT=16)

2007-01-24 Thread Stijn Tintel
Goswin von Brederlow wrote: grep devpts /etc/init.d/* You must be missing one of the packages that usualy mount it. MfG Goswin It is there .. The problem was that /dev/pts didn't exist, which caused the mount of devpts to fail. Maybe this is because I'm not running udev inside the

Bug#408093: linux-image-2.6.18-3-xen-686: CONFIG_LEGACY_PTY_COUNT=16

2007-01-23 Thread Stijn Tintel
Package: linux-image-2.6.18-3-xen-686 Version: 2.6.18-7 Severity: important The Debian (Xen) kernel images are compiled with CONFIG_LEGACY_PTY_COUNT=16. This number is extremely low, and you hit that limit very fast, which results in various problems. From the Linux kernel configuration: The

Bug#408093: closed by Bastian Blank (Re:Bug#408093: linux-image-2.6.18-3-xen-686: CONFIG_LEGACY_PTY_COUNT=16)

2007-01-23 Thread Stijn Tintel
Bastian The machine were I reported this problem from, is running Debian Etch + Xen. Everything is installed from packages from the Etch repository, no self-built packages, etc. In the dom0, there doesn't seem to be a problem with PTY's, eg. Unix PTY's are used. Output of who on dom0

Bug#373227: closed by [EMAIL PROTECTED] (Jaldhar H. Vyas) (Bug#373227: fixed in dovecot 1.0.beta8-4)

2006-06-14 Thread Stijn Tintel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Debian Bug Tracking System wrote: We believe that the bug you reported is fixed in the latest version of dovecot, which is due to be installed in the Debian FTP archive: dovecot-common_1.0.beta8-4_i386.deb to

Bug#373227: dovecot: child 7590 (auth-worker) killed with signal 11

2006-06-13 Thread Stijn Tintel
Package: dovecot Version: 1.0.beta8-3 Severity: grave Justification: renders package unusable After doing aptitude update / dist-upgrade tonight, I cannot authenticate to my dovecot mailserver anymore. I enabled debugging both for mail and auth, but I didn't find anything useful in the logs.

Bug#352313: samba: only master browser server is shown in workgroup

2006-02-15 Thread Stijn Tintel
Steve Langasek wrote: Hmm, interesting. I did notice that line in your smb.conf as being out of the ordinary and probably unnecessary, but I didn't suspect it of causing the problem. I think (created the initial samba configs several years ago, so I don't remember this for sure) I'm using

Bug#352313: samba: only master browser server is shown in workgroup

2006-02-14 Thread Stijn Tintel
Steve Langasek wrote: Ok. Can you confirm the version of the samba package installed on a machine that's showing this problem, as send us the output of ls -l /var/lib/samba/ /var/cache/samba/ /var/run/samba/ on the affected machine? It appears that after reinstalling the Debian Samba packages

Bug#352313: samba: only master browser server is shown in workgroup

2006-02-14 Thread Stijn Tintel
Steve Langasek wrote: There still is this other box in another workgroup however, where I also installed those packages I made without the FHS patch to see if it would solve the problem there. Even without the FHS patch, the workgroup that box is master browser for, you never guess, only shows

Bug#352313: samba: only master browser server is shown in workgroup

2006-02-14 Thread Stijn Tintel
Steve Langasek wrote: What's the rest of the smb.conf? In particular, what are the values of interfaces and wins server? interfaces = 192.168.1.0/24 127.0.0.0/8 wins server = 10.69.0.1 Ok. And the GATEWAY-CO machine is currently showing the problem? Exactly. Can you also forward the

Bug#352313: samba: only master browser server is shown in workgroup

2006-02-14 Thread Stijn Tintel
Steve Langasek wrote: On Wed, Feb 15, 2006 at 03:33:29AM +0100, Stijn Tintel wrote: Steve Langasek wrote: What's the rest of the smb.conf? In particular, what are the values of interfaces and wins server? interfaces = 192.168.1.0/24 127.0.0.0/8 Ok. For the record, this is not valid

Bug#352313: samba: only master browser server is shown in workgroup

2006-02-14 Thread Stijn Tintel
Steve Langasek wrote: Ok; cc:ing the BTS again, so that this is documented for others. On Wed, Feb 15, 2006 at 03:42:45AM +0100, Stijn Tintel wrote: browse.dat: snip The browse.dat shows that your DMB can see the DMBs for a number of other workgroups, but it is not seeing any other servers

Bug#352313: samba: only master browser server is shown in workgroup

2006-02-10 Thread Stijn Tintel
Package: samba Version: 3.0.21b-1 Severity: important Since Samba version 3.0.21 has enterted Debian, the only samba server that show up in my network neighbourhood is the master browser server. Other boxes can not be seen. I found this problem to be caused by the FHS patch. I apt-get source'd

Bug#341314: iptables -m owner fails with 'Invalid argument'

2005-11-29 Thread Stijn Tintel
Package: iptables Version: 1.3.3-2 Severity: normal The following commands fail with 'ip6tables: Invalid argument': ip6tables -A OUTPUT -m owner --uid-owner 0 -j ACCEPT ip6tables -A OUTPUT -m owner --gid-owner 0 -j ACCEPT I tested them on another box running Debian Sarge, and those commands