OpenSolaris

Printable Version Enter a New Search
Bug ID 6619347
Synopsis SunSSH is not fully compatible with RFC4254 with regard to port forwarding
State 10-Fix Delivered (Fix available in build)
Category:Subcategory ssh:other
Keywords
Responsible Engineer Jan Pechanec
Reported Against
Duplicate Of
Introduced In solaris_9
Commit to Fix snv_77
Fixed In snv_77
Release Fixed solaris_nevada(snv_77)
Related Bugs 6506674 , 6620419
Submit Date 19-October-2007
Last Update Date 8-November-2007
Description
while working on "6506674 allow specific binding address to be used with -LRD options for ssh(1)" it was found out that SunSSH doesn't treat "0.0.0.0" as an alias for all IPv4 addresses as requested by RFC 4254, section 7.1. It is incorrectly treated as an alias for all IPv4 AND IPv6 addresses. While this doesn't seem to be a problem now it could be in the future. This bug came from OpenSSH from which we forked. (btw. an empty string "" is the correct RFC 4254 compliant alias for all protocol families supported on the server side).

OpenSSH already fixed this in OpenSSH 4.0p1 release and introduced SSH_OLD_FORWARD_ADDR compatibility flag so that old clients can be treated in a backward compatible way. All OpenSSH versions before 4.0 were flagged with this flag in compat.c file. SunSSH is based on 3.5 version so we should also flag all our existing versions - Sun_SSH_1.0, 1.0.1 and 1.1 with such a flag, and then fix this uncompatibility.

this means that we need a version bump to distinguish between older, not fully RFC compliant SunSSH releases, and the new one. We should change the version from 1.1 to 1.2 together with the code change for 6506674.

this will need a PSARC case. 6506674 will be left out from PSARC/2007/034 and will form, together with this CR, a new ARC case.
Work Around
N/A
Comments
N/A