The provided patch seems to fix the problem for me:
lgb@vega:/tmp/openssl-1.0.1$ ssh abydos
Segmentation fault (core dumped)
lgb@vega:/tmp/openssl-1.0.1$ env LD_LIBRARY_PATH=`pwd` ssh abydos
ssh: /tmp/openssl-1.0.1/libcrypto.so.1.0.0: no version information available
(required by ssh)
X11 forward
And btw, I have this problem with trying to ssh a Debian based (though
quite old) Zorp firewall box ("ZorpOS").
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/968753
Title:
ssh cras
This affects me too, my bugreport (which had some gdb output in the hope
it can be useful) is bug 970180
However that report is marked a duplicate of this one for now.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
@Jonas: Yes, I could figure out (even that comment helped you've
mentioned as well) just I am wondering why it's useful to break the
compatibility, when SSHD_OPTS can be used here, so I don't need to edit
a new file to preserve the functionality I've configured in the previous
version of the system
It seems options set in /etc/default/ssh is not used when launching sshd
with "service ssh start" but it does if I do "/etc/init.d/ssh start". So
even if I have -4 sshd option to workaround the IPv6 problem, it is not
used by default ...
--
ssh X11 forwarding does not work
https://bugs.launchpad.
** Summary changed:
- X11 forwarding does not work
+ ssh X11 forwarding does not work
--
ssh X11 forwarding does not work
https://bugs.launchpad.net/bugs/657302
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubunt
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/657302/+attachment/1680173/+files/Dependencies.txt
** Attachment added: "SSHDConfig.txt"
https://bugs.launchpad.net/bugs/657302/+attachment/1680174/+files/SSHDConfig.txt
--
X11 forwarding does not work
https://bugs.
Public bug reported:
I have problems with X11 forwarding via SSH both with lucid and maverick. On
both of these systems it simply does not work
saying (for example):
xterm Xt error: Can't open display:
xterm: DISPLAY is not set
In /var/log/auth.log I can find this:
Oct 9 13:46:45 oxygene ss
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/34093438/Dependencies.txt
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/34093439/XsessionErrors.txt
--
Command host chooses another DNS server to query than I specified
https://bugs.launchpad.n
Public bug reported:
Binary package hint: bind9
l...@vega:~$ host -t ns ibm.com. nsm.invitel.net.
Using domain server:
Name: 62.77.203.10
Address: 62.77.203.10#53
Aliases:
[...]
Whatever I specify at the end of the command line for command "host", it
seems the queried server is always 62.77.203
I unable to reproduce it either, but it was reproducable then. So I
suppose this bug is already fixed and/or there was some problem with my
config. I set the status to invalid then, if it's OK. Thanks!
** Changed in: openssh (Ubuntu)
Status: Incomplete => Invalid
--
X11 forwarding via SSH
Also I am not sure if it's related but if I do X forwarding via SSH
_from_ that karmic box, it works, but I got this message too:
Warning: No xauth data; using fake authentication data for X11
forwarding.
But sine it works anyway it does not matter too much for me, the problem
is about starting X
Public bug reported:
I had a proper configuration on jaunty (sshd_config) so I could ssh into
that machine and run X11 applications there with X11 forwarding, so I
could use apps fromt here remotely. After upgrade to karmic (same
sshd_config on the server, client is not changed) I got this (for
ex
13 matches
Mail list logo
