<a target='_blank' title='ImageShack - Image And Video Hosting' href=' http://img215.imageshack.us/i/picture12am.png/'> <img src='http://img215.imageshack.us/i/picture12am.png/' border='0'/></a>
I assure you it is ssh2 and is set for des. normally 3des is the default. none of the other available Ciphers work, when i tried to edit the config file and restart ssh it crashed, went into maintainence mode and refused to start. Not sure if the Ciphers line has to go at a specific spot in the config or not...but it gave me trouble when i put it at the end. When i DO connect, it DOESN'T seem to ACTUALLY use des, because i get this error/warning No valid ciphers for protocol version 2 given, using defaults. This is quite annoying, why does SunSSH ship like this? I'd really appreciate a valid config which can use any of the follow from this screenshot: <a target='_blank' title='ImageShack - Image And Video Hosting' href=' http://img5.imageshack.us/i/picture13gg.png/'><img src=' http://img5.imageshack.us/img5/3070/picture13gg.png' border='0'/></a> On Sun, Feb 7, 2010 at 12:46 PM, Bayard Bell < buffer.g.overf...@googlemail.com> wrote: > You shouldn't be able to use des at all if you're using v2 of the protocol. > Perhaps the problem isn't your choice of ciphers but using ssh v1 or setting > ciphers for the wrong version? > > Using iTerm allows you to use the native ssh client so that you don't have > to fiddle with these settings in an alternate client that's glued in > directly with the terminal client. I'd be concerned if it's showing you CBC > cipher variants if it's not showing you the non-CBC versions or not warning > you to use these only with a server that doesn't give you better choices, > and I'd think that a client that's asking you to make these kinds of manual > selections is more than a little broken, minimally at the design level. I > use iTerm with the native ssh to access OpenSolaris, and I've never had to > change the ciphers on either end from defaults. > > I believe ssh -vvv <hostname> on the client side will show you more of the > crypto negotiation to assist you in debugging, while you can run sshd -ddd > to get the server-side debug. > > Am 7 Feb 2010 um 16:22 schrieb Thomas Burgess: > > I normally use JellyFiSSH as my ssh tool on osx, and with every other os, >> it has no problems with any of the ssh encryption protocols. The default is >> 3des but it has many to chose from (blowfish, 3des-cbc, cast128-cbc, >> blowfish-cbc, arcfour, aes256-cbc) >> >> OpenSolaris doesn't allow me to use ANY of these, the only ciper i can >> chose is des, but when i actually connect i get this (error/warning?) >> >> >> No valid ciphers for protocol version 2 given, using defaults. >> >> how do i fix this? >> >> i looked in the config but it all looks correct >> -- >> This message posted from opensolaris.org >> _______________________________________________ >> opensolaris-discuss mailing list >> opensolaris-discuss@opensolaris.org >> > >
_______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
