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.
Bug 603747 - error in section 2.2. Server Security
Summary: error in section 2.2. Server Security
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Security_Guide
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Scott Radvan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 547583
TreeView+ depends on / blocked
 
Reported: 2010-06-14 13:30 UTC by Karel Srot
Modified: 2015-04-07 03:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-22 10:23:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Karel Srot 2010-06-14 13:30:42 UTC 
Description of problem:

1. section 2.2.1.1.2. TCP Wrappers and Attack Warnings
instead of a command
'ALL : 206.182.68.0 : spawn /bin/ 'date' %c %d >> /var/log/intruder_alert'
there should be probably
'ALL : 206.182.68.0 : spawn /bin/echo `date` %c %d >> /var/log/intruder_alert'
or
'ALL : 206.182.68.0 : spawn /bin/echo `/bin/date` %c %d >> /var/log/intruder_alert'

2. section 2.2.8. Verifying Which Ports Are Listening
The text contains:

cat /etc/services | grep 834  (command)
This command returns no output...

Probably there should be something like
This command returns no output related to the port 834. (Since there are lines found which are related to ports 1834, 2834 and 3834)


Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 6
Security Guide
A Guide to Securing Red Hat Enterprise Linux
Edition 1.5
Comment 1 RHEL Program Management 2010-06-14 13:43:00 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 2 Scott Radvan 2010-06-14 21:59:06 UTC 
fixed in source, will appear on redhat.com when next published - thanks!
Comment 3 Zbysek MRAZ 2010-08-13 11:39:35 UTC 
I went thru the online Security Guide Edition 1.5 today and found following problems:

Old fixes:
1. section 2.2.1.1.2. TCP Wrappers and Attack Warnings
There is still '' instead of `` within the example:
ALL : 206.182.68.0 : spawn /bin/echo 'date' %c %d >> /var/log/intruder_alert 
So the output will look like 
date 206.182.68.0 sshd
instead of
Fri Aug 13 10:25:29 CEST 2010 206.182.68.0 sshd


New problems I found:
section 2.2.2.2. Protect portmap With iptables

In the example
iptables -A INPUT -p tcp -s! 192.168.0.0/24 --dport 111 -j DROP
the system will warn about obsoleteness 
please use
iptables -A INPUT -p tcp ! -s 192.168.0.0/24 --dport 111 -j DROP
as well as in the next example where will be:
iptables -A INPUT -p udp ! -s 192.168.0.0/24  --dport 111 -j DROP


2, section 2.2.6.3.1. Restricting User Accounts
To disable specific user accounts in vsftpd, add the username to /etc/vsftpd.ftpusers

This file does not exist and default pam configuration points to /etc/vsftpd/ftpusers file. So the correct one to mention is /etc/vsftpd/ftpusers

Please take a look at it.
Note You need to log in before you can comment on or make changes to this bug.