This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected Fedora versions. For comments that are specific to the vulnerability please use bugs filed against "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When creating a Bodhi update request, please include this bug ID and the bug IDs of this bug's parent bugs filed against the "Security Response" product (the top-level CVE bugs). Please mention the CVE IDs being fixed in the RPM changelog when available. Bodhi update submission link: https://admin.fedoraproject.org/updates/new/?type_=security&bugs=820414 Please note: this issue affects multiple supported versions of Fedora. Only one tracking bug has been filed; please ensure that it is only closed when all affected versions are fixed. [bug automatically created by: add-tracking-bugs]
There is no upstream fix, and the upstream author has no intention of fixing the problem, or in continuing to maintain the software, as noted in the vulnerability report. I think that, unless we want to invest in finding an appropriate fix and maintaining this ourselves, we should remove rssh from Fedora and EPEL, due to upstream's disinterest in maintaining it.
I have orphaned the package. If anyone doesn't want to take over and fix the security issue, they will have to retire it. I know OLPC is using this package so I am giving them a chance to deal with this first.
Could OLPC use scponly instead?
(In reply to comment #3) > Could OLPC use scponly instead? They can probably just configure OpenSSH properly, for example by using ForceCommand=internal-sftp according to the sshd_config man page.
(In reply to comment #2) > I have orphaned the package. If anyone doesn't want to take over and fix > the security issue, they will have to retire it. I know OLPC is using this > package so I am giving them a chance to deal with this first. Any progress with having this package retired?
Patch is in bug 877279 comment 15.
rssh-2.3.4-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2012-20111/rssh-2.3.4-1.fc18
rssh-2.3.4-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/FEDORA-2012-20109/rssh-2.3.4-1.fc17
rssh-2.3.4-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/rssh-2.3.4-1.fc16
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Package rssh-2.3.4-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing rssh-2.3.4-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-20236/rssh-2.3.4-1.fc16 then log in and leave karma (feedback).
rssh-2.3.4-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
rssh-2.3.4-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.