+++ This bug was initially created as a clone of Bug #695781 +++ > What is the nature and description of the request? Man page clarification. In the ssh utilities, IPv6 addresses need to be enclosed in square brackets "[]". The man page specifies this in descriptions of port forwarding options, but there is no other indication of this requirement. > Why does the customer need this? (List the business requirements here) Clarification of this requirement in the man pages makes usage either. Initially the customer thought IPv6 was not working at all since this detail was not specified. > How would the customer like to achieve this? (List the functional > requirements here) A simple "IPv6 note" in all the ssh man pages. A note could also be added for the "-6" switch description, however that option is only to force IPv6, so the square bracket necessity can apply to other cases as well. > For each functional requirement listed in question 4, specify how Red Hat and > the customer can test to confirm the requirement is successfully implemented. N/A > Is there already an existing RFE upstream or in Red Hat bugzilla? Not that I can find. > How quickly does this need resolved? (desired target release) No hard deadline but this is very minor documentation. > List the affected packages openssh
*** Bug 695782 has been marked as a duplicate of this bug. ***
This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.8 and Red Hat does not plan to fix this issue the currently developed update. Contact your manager or support representative in case you need to escalate this bug.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0073.html