Closed bpiwowar closed 7 years ago
While I appreciate the convenience of having things work out of the box, it doesn’t seem nice to pollute the LC_*
namespace to “tunnel” information.
I am thinking that a user who need the RMATE
variables and cannot loosen the “security policy” could use LC_FORWARD_*
and then for any LC_FORWARD_«foo»
variable, their .profile
would set «foo»
to its value, so basically a general variable tunneling system.
Another solution could maybe be to support variables in the config file, so a user could put $LC_RMATE_PORT
or somesuch for the port number, but it seems maybe too complex, though I’d really prefer not to hardcode LC_*
variable in rmate
.
Yes, I should have thought of this solution which is much simpler.
This allows to go through stricter SSH server policies that only allow LC_* variables through