> ok, i found some more diagnostic messages in /sys/log/sshdebug:
> ...
> The problem might be that `dh.c` has an empty implementation of `dh_client142`
> ...
Ingo,
I must admit to being the guilty party for the SSHv2 implementation.
Though Geoff gets credit for cleaning up what was some of my
ugl
Actually openssh-6.7 disabled some "insecure" key exchange algorithms and
ciphers and the pln9 netssh command seems to offer some key exchange that it
does not support fully.
To allow communication with openssh-6.7 servers, as used to with <=openssh-6.6
servers, it seems most convenient to me,
ok, i found some more diagnostic messages in /sys/log/sshdebug:
p9 Jan 21 10:55:48 netssh: client user @192.168.1.12 id 0 id
string `SSH-2.0-OpenSSH_6.7p1-hpn14v5
p9 Jan 21 10:55:48 netssh: client user @192.168.1.12 id 0 sent KEX
algs: diffie-hellman-group1-sha1,diffie-hellman-gr
Hi,
the netssh key exchange seems to be incompatible with openssh-6.7.
I installed a new version of openssh on a gentoo host recently, that
automatically came in as a stable update package for a gentoo-amd64 system:
OpenSSH_6.7p1-hpn14v5, OpenSSL 1.0.1k 8 Jan 2015
When calling this sy
i had to tweak srvssh to work with ssh2. if this looks reasonable, i'll
send in a patch.
diff /n/dump/2013/0414/rc/bin/srvssh /rc/bin/srvssh
84c84
< 'ssh '$rawflags' '$1' '$rawhack' '$u9fspath' -na none -u ''$''USER -l
''$''HOME/u9fs.log' \
---
> 'ssh '$rawflags' '$1' '$rawhack' '''$u9fspath' -na
pull, recompile and try again (kill all netssh processes first).
host key verification isn't working so it's been temporarily disabled.
Perhaps I should add that when I did this the following message appeared on the
screen:
14:11:39 netssh: server id 0 new connection on fd 6
Thanks,
James
On Apr 24, 2012, at 1:17 PM, James Chapman wrote:
> Hi,
>
> I'm very pleased to see the new progress with ssh2. I thought I'd try it out
Hi,
I'm very pleased to see the new progress with ssh2. I thought I'd try it out
but I didn't get very far.
I just did a pull from sources and built a new kernel.
I tried the following:
cpu% ssh user@host
The following key has been offered by the server:
ek=23 n=
Add this key? (yes, no, se
