Re: [osol-discuss] SunSSH server warning about Cipers

2010-02-08 Thread Thomas Burgess
> > hi Thomas, frankly, if the SSH server refused to start after the > config was changed, it must have been broken which could probably happen > with OpenSSH as well. > > Yes, i figured that much =) I found the log which showed the error but it didn't give an exact enough message saying w

Re: [osol-discuss] SunSSH server warning about Cipers

2010-02-08 Thread Thomas Burgess
>you mean the log on the server side, right? What was the error > message that was not clear? If it's really not clear, it could be fixed. > > > Yes, server side. It showed me the line, and it said that it was a problem with what i had put for Cipers but it didn't tell me WHICH ciphers wer

Re: [osol-discuss] SunSSH server warning about Cipers

2010-02-08 Thread Jan Pechanec
On Mon, 8 Feb 2010, Thomas Burgess wrote: >> hi Thomas, frankly, if the SSH server refused to start after the >> config was changed, it must have been broken which could probably happen >> with OpenSSH as well. >> >> >Yes, i figured that much =) I found the log which showed the error but

Re: [osol-discuss] SunSSH server warning about Cipers

2010-02-08 Thread Jan Pechanec
On Sun, 7 Feb 2010, Thomas Burgess wrote: >it makes sense but when i tried to enable the cipers in the config file ssh >refused to start and stayed in maintainence mode. It took me 20 minutes 2 >reboots and 20 commands to get it to start back upthis is really >frustrating. >I'd rather just ha

Re: [osol-discuss] SunSSH server warning about Cipers

2010-02-08 Thread Jan Pechanec
On Sun, 7 Feb 2010, Matt Lewandowsky wrote: >I have seen this also, with older version of a certain popular Windows >SSH client which shall remain unnamed. It's surely a client problem. >The only potential flaw on the server's side is that it's not giving >you a more "human-friendly" error mess

Re: [osol-discuss] SunSSH server warning about Cipers

2010-02-08 Thread Lasse Osterild
On 07/02/2010, at 18.59, Thomas Burgess wrote: > 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 su

Re: [osol-discuss] SunSSH server warning about Cipers

2010-02-07 Thread Matt Lewandowsky
gt; To: opensolaris-discuss@opensolaris.org > Subject: [osol-discuss] SunSSH server warning about Cipers > > 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 ha

Re: [osol-discuss] SunSSH server warning about Cipers

2010-02-07 Thread Thomas Burgess
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 th

Re: [osol-discuss] SunSSH server warning about Cipers

2010-02-07 Thread Thomas Burgess
it makes sense but when i tried to enable the cipers in the config file ssh refused to start and stayed in maintainence mode. It took me 20 minutes 2 reboots and 20 commands to get it to start back upthis is really frustrating. I'd rather just have OpenSSH oh well I'll try again i guess

Re: [osol-discuss] SunSSH server warning about Cipers

2010-02-07 Thread Bayard Bell
The error message is the client telling you that DES isn't a supported cipher. That's not an issue with anyone's SSH as you seem to suggest– it's the client telling you that a choice that's outside the protocol spec can't be accepted. Thus far the evidence is that you're working backwards fr

Re: [osol-discuss] SunSSH server warning about Cipers

2010-02-07 Thread Bayard Bell
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

Re: [osol-discuss] SunSSH server warning about Cipers

2010-02-07 Thread A Hettinger
The cbc cyphers are not enabled by default because all of them have been broken: https://www.kb.cert.org/vuls/id/958563 the default cypher-list is: aes128-ctr,aes192-ctr,aes256-ctr,arcfour128,arcfour256,arcfour I'm not sure why it didn't go with arcfour, but I would strongly recommend upgradin

Re: [osol-discuss] SunSSH server warning about Cipers

2010-02-07 Thread Dennis Clarke
> 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

[osol-discuss] SunSSH server warning about Cipers

2010-02-07 Thread 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