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 651820 - sftp fails if users .bashrc outputs to stderr
Summary: sftp fails if users .bashrc outputs to stderr
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: openssh
Version: 6.0
Hardware: All
OS: Linux
urgent
high
Target Milestone: rc
: ---
Assignee: Jan F. Chadima
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On: 631757
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-10 11:36 UTC by RHEL Program Management
Modified: 2010-12-06 08:26 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When the ~/.bashrc startup file contained a command that produced an output to standard error (STDERR), the sftp utility was unable to log in to that account. This bug has been fixed, and the output to STDERR no longer prevents sftp from establishing the connection.
Clone Of:
Environment:
Last Closed: 2010-12-06 08:26:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
sshd_config from test for CVE-2009-2904 (3.76 KB, text/plain)
2010-11-14 12:40 UTC, Miroslav Vadkerti
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2010:0943 0 normal SHIPPED_LIVE openssh bug fix update 2010-12-06 08:26:39 UTC

Description RHEL Program Management 2010-11-10 11:36:33 UTC
This bug has been copied from bug #631757 and has been proposed
to be backported to 6.0 z-stream (EUS).

Comment 5 Jaromir Hradilek 2010-11-12 13:20:40 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When the ~/.bashrc startup file contained a command that produced an output to standard error (STDERR), the sftp utility was unable to log in to that account. This bug has been fixed, and the output to STDERR no longer prevents sftp from establishing the connection.

Comment 8 Miroslav Vadkerti 2010-11-14 12:40:32 UTC
Created attachment 460366 [details]
sshd_config from test for CVE-2009-2904

Comment 9 Miroslav Vadkerti 2010-11-16 13:38:12 UTC
Moving to ON_QA

Comment 14 errata-xmlrpc 2010-12-06 08:26:46 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0943.html


Note You need to log in before you can comment on or make changes to this bug.