Bug#785441: Support maintainer name and email address
Idézem/Quoting Stephen Gelman : tags 785441 -patch thanks -- Viktor, This seems like a reasonable idea, however I do not see a patch attached to the bug. If you have one could you please send it? Thanks! Stephen Hello Stephen! I've lost the solution, and really the problem too. I think the format "Stephen Gelman " causes a problem. I hope you could eliminate *all* 'eval'-s. All the best! SZÉPE Viktor, webes alkalmazás üzemeltetés / Running your application https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md ~~~ ügyelet/hotline: +36-20-4242498 s...@szepe.net skype: szepe.viktor Budapest, III. kerület
Bug#886544: redis-server: Replacing set -e in sysvinit script
Idézem/Quoting Chris Lamb : Chris Lamb wrote: > Please see the original report citing why "set -e" is not something to > be considered in an init script. I have re-read this and do not understand the rationale. In my experienece, `set - e` ensures that the script is not full of error checking code that is, in- itself, prone to errors. > > I further don't see how a preference for init system is relevant here. > > As the init script is only for SysVinit, not systemd. Sure, and redis supports sysvinit so I don't see why mentioning a dislike for systemd is relevant, yet alone productive...? Gentle ping on this bug? Thank you. You may close it, as my wish was to have set -e -less Redis init script. SZÉPE Viktor, honlap üzemeltetés / Running your application https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md -- ügyelet/hotline: +36-20-4242498 s...@szepe.net skype: szepe.viktor Budapest, III. kerület
Bug#886544: redis-server: Replacing set -e in sysvinit script
Thank you for your answer. Idézem/Quoting Chris Lamb : The only purpose of this bug is to have a non-"set -e" redis package in Debian. I think I'm missing something here. I don't understand the rationale or motivation behind wanting to remove set -e. The scripts work fine as they are, unless you are reporting a bug..? Please see the original report citing why "set -e" is not something to be considered in an init script. I am a SysVinit user as systemd may harm my clients' servers. I further don't see how a preference for init system is relevant here. As the init script is only for SysVinit, not systemd. SZÉPE Viktor, honlap üzemeltetés / Running your application https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md -- ügyelet/hotline: +36-20-4242498 s...@szepe.net skype: szepe.viktor Budapest, III. kerület
Bug#886544: redis-server: Replacing set -e in sysvinit script
Idézem/Quoting Chris Lamb : Chris Lamb wrote: I don't want to play "severity wars" but I'm not sure what the exact problem it is you are reporting here. […] Gentle ping on this (perhaps non-Debian?) bug Hello Chris! The only purpose of this bug is to have a non-"set -e" redis package in Debian. That is why I've proposed /lib/init/init-d-script It is fun to write those tiny scripts! I am a SysVinit user as systemd may harm my clients' servers. All the best to you! SZÉPE Viktor, honlap üzemeltetés / Running your application https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md -- ügyelet/hotline: +36-20-4242498 s...@szepe.net skype: szepe.viktor Budapest, III. kerület
Bug#888837: thx for the hot-fix
I think the current rules are still 3.4.1-incompatible: $ host -t TXT 1.4.3.updates.spamassassin.org. 1.4.3.updates.spamassassin.org is an alias for 3.3.3.updates.spamassassin.org. 3.3.3.updates.spamassassin.org descriptive text "1822773" $ wget -qO- https://svn.apache.org/repos/asf/spamassassin/site/updates/MIRRORED.BY|tail #CONTACT: tobisworld gmail http://sa-update.verein-clean.net/ weight=10 #CONTACT: Jari Fredriksson (jarif) http://sa-update.bitwell.fi/ weight=10 #CONTACT: sysadm...@spamassassin.apache.org http://sa-update.spamassassin.org/ weight=10 $ wget -qS http://sa-update.spamassassin.org/1822773.tar.gz HTTP/1.1 200 OK Date: Wed, 31 Jan 2018 19:17:47 GMT Server: Apache/2.4.6 (CentOS) Last-Modified: Wed, 31 Jan 2018 08:31:02 GMT ETag: "33afb-5640e4ca8bd80" Accept-Ranges: bytes Content-Length: 211707 Keep-Alive: timeout=5, max=100 Connection: Keep-Alive Content-Type: application/x-gzip $ tar -xf 1822773.tar.gz $ grep -C3 "check_for_forged_gmail_received_headers" 20_head_tests.cf header FORGED_YAHOO_RCVDeval:check_for_forged_yahoo_received_headers() describe FORGED_YAHOO_RCVD 'From' yahoo.com does not match 'Received' headers header FORGED_GMAIL_RCVDeval:check_for_forged_gmail_received_headers() describe FORGED_GMAIL_RCVD 'From' gmail.com does not match 'Received' headers header __FORGED_JUNO_RCVD eval:check_for_forged_juno_received_headers() There is no version constrain for FORGED_GMAIL_RCVD Noah: Do you see a resolution? SZÉPE Viktor, honlap üzemeltetés https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md -- +36-20-4242498 s...@szepe.net skype: szepe.viktor Budapest, III. kerület
Bug#865051: fail2ban: Fails to start after Jessie to Stretch upgrade due to no accessible config files
Idézem/Quoting Yaroslav Halchenko : On Wed, 31 Jan 2018, Przemysław Pawełczyk wrote: ERROR Unable to read the filter ERROR Errors in jail 'ssh-ddos'. Skipping... It seems that ssh and ssh-ddos were renamed in jail.conf to sshd and sshd-ddos. So I had to edit /etc/fail2ban/jail.local to replace [ssh] with [sshd] and [ssh-ddos] with [sshd-ddos]. It fixed the problem. (Not strictly bug related, but it's worth to note that ipset lists are no longer named fail2ban-ssh and fail2ban-ssh-ddos, but f2b-sshd and f2b-sshd-ddos now.) indeed, there should have probably been a NEWS entry for that upgrade to state about configuration file(s) changes. Sorry about that. Not sure though if it is worthwhile uploading a new version merely with the NEWS entry for it Yes, it is. NEWS is very eye-catching. SZÉPE Viktor, honlap üzemeltetés https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md -- +36-20-4242498 s...@szepe.net skype: szepe.viktor Budapest, III. kerület
Bug#888837: hot-fix: adding "check_for_forged_gmail_received_headers"
The quickest work-around if to add check_for_forged_gmail_received_headers() to source code. Add the register_eval_rule line and the function itself: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/HeaderEval.pm?view=markup but debsums will complain. SZÉPE Viktor, honlap üzemeltetés https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md -- +36-20-4242498 s...@szepe.net skype: szepe.viktor Budapest, III. kerület
Bug#888711: fail2ban fails to start sshd-ddos filter.
Idézem/Quoting Peter Chubb : Package: fail2ban Version: 0.10.2-1 Severity: normal Dear Maintainer, After upgrading fail2ban, it no longer starts. The error message is: fail2ban Failed during configuration: Bad value substitution: option 'mode' in section 'Definition' contains an interpolation key 'ddos' which is not a valid option name. Raw value: '%(ddos)s' The problem is in /etc/fail2ban/filter.d/sshd-ddos.conf It seems to be that the sshd-ddos filter has been merged into sshd. Please see sshd.conf for details and remove sshd-ddos.conf and set [sshd] mode = ddos. I hope this helps you. SZÉPE Viktor, honlap üzemeltetés https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md -- +36-20-4242498 s...@szepe.net skype: szepe.viktor Budapest, III. kerület
Bug#770171: great job tiziano
Idézem/Quoting Sebastian Walther : hi there, i surprisingly discovered today that fail2ban didn't work for quite some (too long) time. Reason was changing from syslog to systemd. after changing "backend = auto" to "backend = systemd" and wondering why it fail all the time, it took me hours to find out that there is a bug/ missing dependency. guys please fix this! this bug is nearly 3 years old!! or is there any technical reason for this? This is not a solution but you may try to install Fail2ban from testing https://packages.qa.debian.org/f/fail2ban.html It is quite old but may help you. SZÉPE Viktor, honlap üzemeltetés https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md -- +36-20-4242498 s...@szepe.net skype: szepe.viktor Budapest, III. kerület
Bug#872715: Compat 10
Please see the new autoreconf policy https://lintian.debian.org/tags/useless-autoreconf-build-depends.html All the best! Viktor -- +36204242498 Ezen a készüléken sok az elütés. Elnézést!
Bug#861425: priority difference
Thank you. I've realized there are override files in a Debian repo. https://github.com/szepeviktor/debian-server-tools/blob/master/debian-image-normalize.sh#L169 Stretch introduced quiet a change in those overridden priorities. All the best! Viktor -- +36204242498 Ezen a készüléken sok az elütés. Elnézést! On April 30, 2017 6:01:48 PM CEST, Julien Cristau wrote: >Control: reassign -1 aptitude >Control: severity -1 minor >Control: retitle -1 aptitude: package priority mismatch > >On Fri, Apr 28, 2017 at 22:40:01 +0200, SZÉPE Viktor wrote: > >> Package: mirrors >> Severity: important >> >> Hello! >> >> The Packages files contains "optional". >> >> $ wget -qO- >http://ftp.debian.org/debian/dists/stretch/main/binary-arm64/Packages.gz|zgrep >> -Fx -A18 "Package: aptitude"|tail -n 1 >> Priority: optional >> >> The package contains "important". >> >> In >> >http://ftp.debian.org/debian/pool/main/a/aptitude/aptitude_0.8.7-1_amd64.deb >> control files has: >> Priority: important >> >> Please advise. > >The Packages file contains the authoritative information, the priority >in the package itself can pretty much be ignored. > >Cheers, >Julien
Bug#861425: priority difference
Package: mirrors Severity: important Hello! The Packages files contains "optional". $ wget -qO- http://ftp.debian.org/debian/dists/stretch/main/binary-arm64/Packages.gz|zgrep -Fx -A18 "Package: aptitude"|tail -n 1 Priority: optional The package contains "important". In http://ftp.debian.org/debian/pool/main/a/aptitude/aptitude_0.8.7-1_amd64.deb control files has: Priority: important Please advise. Thanks. -- System Information: Debian Release: 8.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/3 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) SZÉPE Viktor https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md -- +36-20-4242498 s...@szepe.net skype: szepe.viktor Budapest, III. kerület
Bug#823807: ITA: courier
Hello Markus! thanks for the pointers. Please note that upstream development of courier and the Debian packaging for courier are somewhat different projects. I've just realized couple of months ago that Courier is intended to be installed and tested on Fedora and other RPM based distros. For the Debian packaging, it's certainly going to be the Debian BTS for bug reporting I'm keeping a list of bugs/todos on GitHub https://github.com/szepeviktor/courier/issues and opening bugs on Debian simultaneously. Please consider - closing very old bugs - removing patches integrated by upstream https://github.com/szepeviktor/courier/commit/bca5316f40bf9335c9ec36db850916481e99cd2c - backporting CNAME fix to Jessie https://github.com/svarshavchik/courier-libs/commit/5e522ab14f45c6f4f43c43e32a2f72fbf6354f1c Should I report the CNAME fix as a Debian bug? Thank you! Idézem/Quoting Markus Wanner : Hello Viktor, thanks for the pointers. Please note that upstream development of courier and the Debian packaging for courier are somewhat different projects. You're mostly mentioning upstream work and issues. I guess upstream needs to decide how they want to work. For the Debian packaging, it's certainly going to be the Debian BTS for bug reporting, as it's tightly integrated with all of the existing Debian infrastructure. But I'm subscribed to the relevant courier-* mailing lists [0] and I'll have a look at the bugs and patches you mentioned. Don't expect me to do feature development for courier, though. Kind Regards Markus Wanner [0]: Please note that I'm subscribed to lots of mailing lists, but I'm certainly not reading all of it. Therefore, please CC me for a heads-up. On 03/23/2017 09:59 PM, SZÉPE Viktor wrote: Would it be possible to enable very easy bug reporting? I have two here: https://github.com/szepeviktor/courier/issues I think discussion in a Debian bug report is quiet hard. On GitHub it is very easy to contribute. Sam merged a lot of Debian patches as you may know. https://github.com/szepeviktor/courier/commit/bca5316f40bf9335c9ec36db850916481e99cd2c And we have final break-through with CNAMEs (Amazon SES, Mailjet etc.) https://github.com/svarshavchik/courier-libs/commit/5e522ab14f45c6f4f43c43e32a2f72fbf6354f1c And you can read on courier-users that many are willing to contribute. All the best to you! SZÉPE Viktor https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md SZÉPE Viktor https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md -- +36-20-4242498 s...@szepe.net skype: szepe.viktor Budapest, III. kerület
Bug#823807: ITA: courier
Idézem/Quoting Markus Wanner : Hi, as a happy long-time [0] user of courier-mta on Debian [0], I'd like to try my best to make that fine MTA stay in Debian. I'm offering to adopt courier, courier-authlib and courier-unicode. I'd welcome all the help I can get and would love to team up with others, as my spare time is pretty limited. Therefore this call to other fellow courier users: please speak up! Kind Regards Markus Wanner Hello Markus!! Would it be possible to enable very easy bug reporting? I have two here: https://github.com/szepeviktor/courier/issues I think discussion in a Debian bug report is quiet hard. On GitHub it is very easy to contribute. Sam merged a lot of Debian patches as you may know. https://github.com/szepeviktor/courier/commit/bca5316f40bf9335c9ec36db850916481e99cd2c And we have final break-through with CNAMEs (Amazon SES, Mailjet etc.) https://github.com/svarshavchik/courier-libs/commit/5e522ab14f45c6f4f43c43e32a2f72fbf6354f1c And you can read on courier-users that many are willing to contribute. All the best to you! SZÉPE Viktor https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md -- +36-20-4242498 s...@szepe.net skype: szepe.viktor Budapest, III. kerület
Bug#823807: Fwd: [courier-users] Future of Courier MTA
Hello! I far away from handling Debian's infrastructure although I run my own public repo http://szepeviktor.github.io/debian/ Let me have here my message sent to courier-users: - Forwarded message from SZÉPE Viktor - Date: Fri, 17 Feb 2017 00:36:06 +0100 From: SZÉPE Viktor Subject: [courier-users] Future of Courier MTA To: courier-users Hello! Honestly I do not know who uses Courier. Maybe no one knows. 1) I am a Debian-only user and it seems no one is maintaining courier-mta. 2) I've never met Exim or Postfix so a switch is not an option for me. 3) I don't use software on Debian without packaging. They are loose files without any control. (That is why I run my own public repo) 4) What are my options for 2017 when I probably switch to Debian stretch? Are big companies with big $$$ using Courier? Is anyone willing to cooperate with me on fixing Debian-related errors? https://github.com/szepeviktor/courier SZÉPE Viktor https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md -- +36-20-4242498 s...@szepe.net skype: szepe.viktor Budapest, III. kerület
Bug#771322: late answer
Excuse me for not answering for your questions. Where should I find your comment in the package regarding this bug? Szépe Viktor -- +36-20-4242498 s...@szepe.net skype: szepe.viktor Budapest, XX. kerület -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769405: Acknowledgement (Adding mx symlink)
Excuse me. I typed the text inplace of additional addresses. Please consider adding an mx symlink to host. It would execute host as host -t MX. Thank you. Idézem/Quoting ow...@bugs.debian.org: Thank you for filing a new Bug report with Debian. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. As you requested using X-Debbugs-CC, your message was also forwarded to Please, Thank (after having been given a Bug report number, if it did not have one). Your message has been sent to the package maintainer(s): LaMont Jones If you wish to submit further information on this problem, please send it to 769...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 769405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems Szépe Viktor -- +36-20-4242498 s...@szepe.net skype: szepe.viktor Budapest, XX. kerület -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701640: s_client doesn't verify cert without -CApath
Subject: s_client doesn't verify cert without -CApath Package: openssl Version: 0.9.8o-4squeeze14 Severity: minor Tags: squeeze -- System Information: Debian Release: 6.0.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-xen-686 (SMP w/1 CPU core) Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openssl depends on: ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libssl0.9.80.9.8o-4squeeze14 SSL shared libraries ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime openssl recommends no packages. Versions of packages openssl suggests: ii ca-certificates20090814+nmu3squeeze1 Common CA certificates -- no debconf information Szépe Viktor -- +36 20 4242498 s...@szepe.net skype: szepe.viktor Budapest, XIV. kerület, Róna utca 121. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#675081: maybe this is not enough
Dear Debian users! Maybe 2 seconds are not enough to stop. You have to wait for proftpd to stop. /etc/init.d/proftpd:176 signal stop 1 sleep 2 start All the best wishes to you all! Szépe Viktor -- +36 20 4242498 s...@szepe.net skype: szepe.viktor Budapest, XIV. kerület, Róna utca 121. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672228: fails to exactly determine whether iptables rule exists
Thank You for this long email! I do no know what these severities mean. All the best wishes! Szépe Viktor Idézem/Quoting Yaroslav Halchenko : NB cross-posting to fail2ban mailing list to seek more feedback GOOD CALL -- although -w wouldn't be the one to catch it since it would stop at '-', e.g: novo# iptables -L -n -v | grep -w fail2ban 0 0 fail2ban-ssh tcp -- * * 0.0.0.0/0 0.0.0.0/0multiport dports 22 but we could anchor it with '\s' novo# iptables -L -n -v | grep 'fail2ban\s' novo# iptables -L -n -v | grep 'fail2ban-ssh\s' 0 0 fail2ban-ssh tcp -- * * 0.0.0.0/0 0.0.0.0/0multiport dports 22 but I cannot find description of \s in man grep and moreover http://stackoverflow.com/questions/4233159/grep-regex-whitespace-behavior suggest to follow a more bullet-prof [ \t] I will probably commit this upstream some time soon and see what people say Could you describe why this deserves 'important' instead of a 'normal' severity? imho it is just normal and would reveal itself only in limited set of cases when anyways probably would trigger reinitialization of all chains returning state to correct operation. thanks again On Wed, 09 May 2012, Szépe Viktor wrote: Package: fail2ban Version: 0.8.4-3 Severity: important Tags: lenny originally: iptables -n -L INPUT | grep -q fail2ban- I think grep needs a "-w". E.g. "ssh" and "ssh-ddos" -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672228: fails to exactly determine whether iptables rule exists
Package: fail2ban Version: 0.8.4-3 Severity: important Tags: lenny originally: iptables -n -L INPUT | grep -q fail2ban- I think grep needs a "-w". E.g. "ssh" and "ssh-ddos" -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-xen-686 (SMP w/1 CPU core) Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fail2ban depends on: ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii python 2.6.6-3+squeeze6 interactive high-level object-orie ii python-central 0.6.16+nmu1 register and build utility for Pyt Versions of packages fail2ban recommends: ii iptables 1.4.8-3administration tools for packet fi ii whois 5.0.10 an intelligent whois client Versions of packages fail2ban suggests: ii heirloom-mailx [mailx]12.4-2 feature-rich BSD mail(1) pn python-gamin (no description available) -- Configuration Files: /etc/fail2ban/fail2ban.conf changed [not included] -- 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#440603: SOLUTION
Add this line set sendmail="/usr/sbin/sendmail" to /etc/mail.rc All the best wishes! Szépe Viktor -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#430166: SOLUTION
Add this line set sendmail="/usr/sbin/sendmail" to /etc/mail.rc All the best wishes! Szépe Viktor -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
