Bug 201268
Summary: | openssh specfile incorrect | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Samuel Stringham <me> | ||||
Component: | openssh | Assignee: | Tomas Mraz <tmraz> | ||||
Status: | CLOSED DEFERRED | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | low | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 4.0 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2006-08-04 06:07:41 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: | |||||||
Attachments: |
|
Description
Samuel Stringham
2006-08-03 21:56:21 UTC
Created attachment 133587 [details]
Patch to remedy problem
This problem will be resolved in a future major release of Red Hat Enterprise Linux. Red Hat does not currently plan to provide a resolution for this in a Red Hat Enterprise Linux update for currently deployed systems. With the goal of minimizing risk of change for deployed systems, and in response to customer and partner requirements, Red Hat takes a conservative approach when evaluating changes for inclusion in maintenance updates for currently deployed products. The primary objectives of update releases are to enable new hardware platform support and to resolve critical defects. I understand RedHat's stance against making changes that would impose risk on its customer base. However, in this case I would like to appeal the decision based on a couple items: 1: The patch is trivial. It does not add/remove code or functionality. 2: openssh-server fails to log to wtmp if a kernel is built without SELinux support. This can present a security risk for those customers that do not/can not use SELinux, and the audit support built in. Might it be more appropriate to just roll this into the next security/quarterly update to openssh? Best, Samuel The problem 2 will be resolved in the package which is planned to be released as a part of the RHEL4 U4 update release. |