Re: SSH2 Optimisation on 68060: findings

2013-06-09 Thread Ingo Jürgensmann
Am 09.06.2013 um 16:27 schrieb Thorsten Glaser : >> Maybe the KEX problem is re-introduced in newest libssh2-1 package. > OpenSSH uses OpenSSL, not libssh, which is a completely > orthogonal, separate implementation of the SSH protocol. Arrakis: ii libssl0.9.70.9.7k-3.1

Re: Fwd: SSH2 Optimisation on 68060: findings

2013-06-09 Thread Thorsten Glaser
Ingo J�rgensmann dixit: (You want to use UTF-8 nowadays.) >Maybe the KEX problem is re-introduced in newest libssh2-1 package. OpenSSH uses OpenSSL, not libssh, which is a completely orthogonal, separate implementation of the SSH protocol. bye, //mirabilos -- [...] if maybe ext3fs wasn't a bet

Re: Fwd: SSH2 Optimisation on 68060: findings

2013-06-09 Thread Andreas Schwab
Ingo Jürgensmann writes: >> After reading up on what this KEX does[1], and why it might be a slight >> security risk to turn it off, I quickly hacked support for it out of the >> openssh source and rebuilt for m68k. There is no need to rebuild the client, setting KexAlgorithms in the ssh config

Fwd: SSH2 Optimisation on 68060: findings

2013-06-09 Thread Ingo Jürgensmann
to login again, but that's not a solution. In 2004 Adam Conrad wrote the following findings about the KEX problem: Anfang der weitergeleiteten Nachricht: > Von: "Adam Conrad" > Betreff: SSH2 Optimisation on 68060: findings > Datum: 28. Februar 2004 11:42:02 MEZ > A