Hide Forgot
Description of problem: What happened to tcpdchk? I think this is really important. In fact, CHANGES references it right at the top.
tcpdchk was removed 16 years ago (the bug #16059), because it was expecting the file /etc/inetd.conf and didn't work with xinetd. The CHANGES mentions this tool, because the file is from upstream project (from 2004 or so [1]). The changelog of the package mentions that these tools were removed (tcpdchk, tcpdmatch): * Mon Aug 14 2000 Jeff Johnson <jbj> - remove utilities that expect /etc/inetd.conf (#16059). but the tcpdmatch was added back in 2010 (bug #604011): * Wed Jun 16 2010 Jan F. Chadima <jchadima> - 7.6-59 - Add modified tcpdmatch (#604011) because it was proved useful. Can you clarify what would you need the tcpdchk for? We could probably do the same with tcpdchk if it would make sense. [1] ftp://ftp.porcupine.org/pub/security/
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Sorry, missed your question at the end. Thanks for the needinfo. In the past, I used it to check files to make sure they were properly formatted. I've also been confused by tcpdmatch, sometimes, so it's nice to check syntax, independently. For example, tcpdmatch seemed like it was working and suggested the right thing, but there were errors pilling up in the journal that I didn't notice until later because of a syntax error. When I first discovered tcpdchk I thought, "Oh, yeah, that tool is obviously necessary for tcpd." If it isn't supposed to be in the package, that's fine, I really thought it was and omitting it was an oversight. I don't know what to suggest, so, whatever you think should be done or not is fine.
Thanks for the clarification. It does not look like a priority at this point. I will leave the bug open if there will be some more demand, we can hack that back, but I don't think it will be the case, since it was not missing for 16 years.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.