Comment 27 for bug 54180

Hello Folks,

I hate to beat an already "terribly beaten horse" but I'd like to say that I would like the null cipher option to be available. The reason being is that working for a WAN optimization company, the need to "see" the unencrypted traffic is paramount in order to reduce SSH's network footprint. In terms of security, most WAN optimization vendors do provide a "secured transport" (IPSEC or SSL-based tunnels) across the WAN to prevent passwords and app-data from being snooped.

Trust me, I do understand the desire to prevent SSH users from shooting themselves and their company's in the foot, however, having a null cipher option does have value - in the WAN opt case, its a business/network-cost-savings value.

Alex