Bug 604111
Summary: | /etc/issue "Kernel \r on an \m" not working as intended? | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | David Barr <redhat> |
Component: | openssh | Assignee: | Jan F. Chadima <jchadima> |
Status: | CLOSED NOTABUG | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.4 | CC: | dmach |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-06-16 05:11:31 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
David Barr
2010-06-15 13:00:27 UTC
I don't think the problem is in /etc/issue. It's probably in how sshd processes it. Reassigning to openssh package. BTW, if I was admin, I wouldn't expose kernel version to anyone who can initiate ssh connection ... Heh. Mine is not to question why /etc/issue was exposed. :) When I get back to the office, I'll test against telnetd in an environment where I can do that, and update whether this is ssh specific. (In reply to comment #1) > I don't think the problem is in /etc/issue. > It's probably in how sshd processes it. > > Reassigning to openssh package. > > > BTW, if I was admin, I wouldn't expose kernel version to anyone who can > initiate ssh connection ... It's intentional the supposed use of issue is to write to potential attacker something like "YOU will be prosecuted according to law ...." but not "You are welcome, our kernel bugs are ....." |