https://bugzilla.mindrot.org/show_bug.cgi?id=2336
--- Comment #5 from Josh Triplett <[email protected]> --- (In reply to Sami Hartikainen from comment #4) > (In reply to Damien Miller from comment #3) > > The reason we haven't done this is that it is when clients start > > forwardings after establishing the shell/login session - these will > > not get into the environment. > > Quite right, a real application requires an additional method for > conveying runtime changes. I've done that, but the implementation is > very much application-specific. Fair point, but let's not let the perfect be the enemy of the good here. Quite a few things don't quite work right with runtime changes or with persistent shared SSH connections, but at least conveying the *initial* data via an environment variable would help. For runtime changes, I'd suggest an environment variable containing a socket that receives notification of changes in a well-defined format. However, that would take quite a lot more work to implement, and the simple environment variable still seems preferable for simple cases. -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ openssh-bugs mailing list [email protected] https://lists.mindrot.org/mailman/listinfo/openssh-bugs
