Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
To avoid port conflicts with services such as CUPS or IMAP
vsftpd
should be using portreserve for reserving respective ports on RHEL6.
Typical changes required:
Given a SysV service package that uses a particular port, (say, krb5_prop/tcp -
754):
1) Create a file named after the service, for example 'krb5_prop', which
contains:
krb5_prop/tcp
2) In the spec, install this file in /etc/portreserve, i.e.,
/etc/portreserve/krb5_prop
3) In the spec, add 'Requires: portreserve' to the package that provides the
server.
4) In the init script, in the start() stanza, add:
[ -x /sbin/portrelease ] && /sbin/portrelease krb5_prop &>/dev/null || :
before starting the daemon.
Some background can be found in bug 103401.
The vsftpd communicates on port 21 with the client that uses port > 1024. There are handled ports for data transfer. This mechanism is the same for TLS too.
No one of that ports is in the range 600-1024. This could be done only by explicit setting in the vsftpd.conf file.
I didn't find any occurrence using port in the range 600-1024 by vsftpd. Therefore I close it with the status 'netabug'.
To avoid port conflicts with services such as CUPS or IMAP vsftpd should be using portreserve for reserving respective ports on RHEL6. Typical changes required: Given a SysV service package that uses a particular port, (say, krb5_prop/tcp - 754): 1) Create a file named after the service, for example 'krb5_prop', which contains: krb5_prop/tcp 2) In the spec, install this file in /etc/portreserve, i.e., /etc/portreserve/krb5_prop 3) In the spec, add 'Requires: portreserve' to the package that provides the server. 4) In the init script, in the start() stanza, add: [ -x /sbin/portrelease ] && /sbin/portrelease krb5_prop &>/dev/null || : before starting the daemon. Some background can be found in bug 103401.