Bug#481072: dk-filter crash seems to be for a specific use case (-k parameter)
On Mon, Aug 16, 2010 at 10:57:35AM +0300, Teodor MICU mteo...@gmail.com wrote: I've been checking the status of 'dk-filter' for squeeze and it is blocked for inclusion by this RC bug report. As far as I can see this reliable crash is reproduced only if you use the -k parameter. I don't use it (I don't have multiple domains) and I don't have crashes, I had only one this morning but that all for almost a year of working properly. I admit that I've been remiss in further investigating this because dk-filter has dropped quite a bit in importance. I'm using this feature myself, so I'm sure it's something to do with the submitter's local configuration. I never did get any strace output to allow me to dig into which of the three calls to dk_sterilize() is actually the issue. That said, I'm not convinced that removing the assert() is a bad idea. It's only used in three places, and in all of those places, it's protected with an if (results ==NULL) return -1. The dk-filter package in Debian is NOT shipping a libdk.so or libdk.a, so there's no risk of affecting any other packages were I to modify the function to e.g. if NULL return NULL in place of the assertion. From my point of view development of dk-filter has stopped and only dkim-filter is maintained properly. Thus this bug and the other I reported will have to be avoided as there are specific use cases. Actually, dkim-filter itself has stopped as well, for the time being, although it is quite stable. The primary contributors to the dkim-filter project have moved on to a fork, opendkim. In conclusion, can we downgrade the severity of this bug report so that at least we have the same version from lenny in squeeze too? If there are no objections I can do this at the end of the week, though it is better to be done by Mike Markley. I don't object, either, but I would also like input from the release team. I can chase that, if you'd like. -- Mike Markley m...@markley.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#481072: dk-filter crash seems to be for a specific use case (-k parameter)
On Wed, Aug 18, 2010 at 12:38 AM, Mike Markley m...@markley.org wrote: On Mon, Aug 16, 2010 at 10:57:35AM +0300, Teodor MICU mteo...@gmail.com wrote: [..] In conclusion, can we downgrade the severity of this bug report so that at least we have the same version from lenny in squeeze too? If there are no objections I can do this at the end of the week, though it is better to be done by Mike Markley. I don't object, either, but I would also like input from the release team. I can chase that, if you'd like. By all means I do prefer to have you as the maintainer of the package to contact the Release team. I'm not sure if this is necessary, but its your call. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#481072: dk-filter crash seems to be for a specific use case (-k parameter)
On Wed, Aug 18, 2010 at 02:37:10AM +0300, Teodor MICU mteo...@gmail.com wrote: By all means I do prefer to have you as the maintainer of the package to contact the Release team. I'm not sure if this is necessary, but its your call. Personally, since I think a simple patch can cause this to not actually halt the filter, I'd prefer to consult the release team and prepare a fixed package. My best guess, at this point, is that the original bug report is due to an issue with the path to the key file. -- Mike Markley m...@markley.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#481072: dk-filter crash seems to be for a specific use case (-k parameter)
Followup-For: Bug #481072 Package: dk-filter Version: 1.0.0.dfsg-1+b1 *** Please type your report below this line *** Hello, I've been checking the status of 'dk-filter' for squeeze and it is blocked for inclusion by this RC bug report. As far as I can see this reliable crash is reproduced only if you use the -k parameter. I don't use it (I don't have multiple domains) and I don't have crashes, I had only one this morning but that all for almost a year of working properly. From my point of view development of dk-filter has stopped and only dkim-filter is maintained properly. Thus this bug and the other I reported will have to be avoided as there are specific use cases. In conclusion, can we downgrade the severity of this bug report so that at least we have the same version from lenny in squeeze too? If there are no objections I can do this at the end of the week, though it is better to be done by Mike Markley. Thanks -- System Information: Debian Release: 5.0.5 APT prefers stable APT policy: (990, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages dk-filter depends on: ii adduser 3.110add and remove users and groups ii libc6 2.7-18lenny4 GNU C Library: Shared libraries ii libmilter1.0.1 8.14.3-5+lenny1 Sendmail Mail Filter API (Milter) ii libssl0.9.8 0.9.8g-15+lenny7 SSL shared libraries dk-filter recommends no packages. dk-filter suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
