I'm not a hard-core ssh expert either, but keep in mind that we're already using the ssh "subsystem" mechanism, ie, we are using an assigned name for the specific service we're trying to reach.
Furthermore, while outside the network spec, implementations like OpenSSH already have the concept of restricting a particular set set of authentication credentials to running a command determined entirely by the server. That is: ie, it is not difficult to lock a particular set of credentials into running only the specific command or subsystem one wants to allow. Small matter of configuration, but one would have to configure credentials in any case, this is just a bit more config. I think the port number thing is more about people who really just want to be able to filter based on port numbers, full stop. I don't, particularly, because forcing encrypted traffic (content the filter can't inspect, by definition) to use port A instead of port B has never struck me as an effective policy enforcement mechanism. YMMV. _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
