On Mon, Jun 18, 2001 at 05:16:28PM -0700, Jason R Thorpe wrote:
> On Tue, Jun 19, 2001 at 09:55:19AM +1000, Luke Mewburn wrote:
> 
>  > Have a look at the way that X11Forwarding is implemented. It effectively
>  > comprises of:
>  > 	* creating a tunnel for the X traffic (ssh & sshd)
>  > 	* creating a one-time $DISPLAY (e.g, "server:55") and and
>  > 	  appropriate xauth cookie for that session (ssh)
>  > 	* passing this new $DISPLAY and cookie (ssh to remote sshd to deal with)
>  > 
>  > Our login(1) can't handle the cookie (or the DISPLAY, unless it's in the
>  > environment before-hand). Hacking login(1) to support this cookie
>  > munging is something that I strongly object to.
> 
> The bug is that OpenSSH has REALLY CRAPPY child environment variable
> handling.

It may do, but AFAICT that has nothing to do with this problem, which
is that X11Forwarding stopped functioning correctly when UseLogin was
enabled.


> (Note that FreSSH does not have the same fundamental problem as OpenSSH
> in this regard, although X11 forwarding is not yet implemented in FreSSH.)

Not having X11 forwarding and xauth cookie munging is, IMHO, fundamental
missing functionality. (Yeah, I know, I have the source. I could add it. :)


Note: I'm not slagging off against FreSSH. I think it's a product with
high potential, and I'm sure I'll use it when features like X11Forwarding
work ok.  I'm just a little bit curious as to why FreSSH was brought up
here when I don't think it is relevent to the problem at hand :-/