e newer short one that just
> exported HISTSIZE, HISTFILE, and ENV=$HOME/.kshrc the XForwarding
> problem disappeared. Don't try this at home, kids, especially at
> 4AM when you're not only old and senile, but tired as hell too. :-)
So what was the fix? What is in the one .
eling.
> You can also look at the "Secure Architectures with OpenBSD" section
> about OpenSSH.
>
> I do not think that the problem is with X server though.
> Best,
> Predrag
>
Yes, you were right. Operator error, it was the nut holding the
steering wheel as usual.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
On Thu, Feb 28, 2008 at 02:46:41AM -0700, Predrag Punosevac sez:
> Denny White wrote:
>
> >-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
> >
> >For the last couple of days I've tried everything I can think of to
> >make XForwarding work with ssh. As
Denny White wrote:
What happens when you try to do the following?
Try to do remote login with as follows
ssh -Y [EMAIL PROTECTED]
you should be now in the shell on the remote host
try to start x client like xdvi or xfig or something like emacs by
typing xdvi
If xdvi pops up that means that
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
For the last couple of days I've tried everything I can think of to
make XForwarding work with ssh. As per the FAQ, I have set it like so:
In sshd_config
X11Forwarding yes
In ssh_config
ForwardAgent yes
ForwardX11 yes
I can use it passably well
5 matches
Mail list logo
