This is from an ssh.com sshd v2.0.x manpage.
Special values to this option
are any, anystd, that allows only standard (see below)
ciphers, and anycipher that allows either any available
cipher or excludes nonencrypting cipher mode none but
allows all others. anystdcipher is the same as above,
but includes only those ciphers mentioned in the IETF-
SecSH-draft (excluding 'none').
As you can see, none is not included with AnyCipher. You'd need to add a comma
and none to the available ciphers for it to work.
--Dave
>Date: Sat, 4 Nov 2000 14:30:02 -0500
>From: Michael Galloway <[EMAIL PROTECTED]>
>To: SSH Mail Exploder <[EMAIL PROTECTED]>
>Subject: Re: -c none appears not to work?
>Mime-Version: 1.0
>Content-Disposition: inline
>User-Agent: Mutt/1.2.5i
>
>hmmm ...
>
>the server config contains:
>
>## Crypto settings
> Ciphers AnyCipher
>
>should that not allow none?
>
>-- michael
>
>Markus Friedl schrieb am Samstag, den 04. November 2000:
>
>> On Fri, Nov 03, 2000 at 09:42:55AM -0500, Michael Galloway wrote:
>> > good day all ...
>> >
>> > attached is an email from one of my users who cannot get the -c none option
to
>> > work on this one host. the host in question has ssh 2.3.0 installed, the
>> > others are at an earlier release of 2.x. i built the 2.3.0 installation and
it
>> > was a vanilla build and install. what are we doing wrong? thanks!
>>
>> as you show, the server does not offer the cipher 'none':
>>
>> > debug: ssh_tr_negotiate_one_alg: failed for c_to_s_cipher: none vs
3des-cbc,blowfish-cbc,twofish-cbc,arcfour,3des-ecb,3des-cfb,3des-ofb,blowfish-ec
b,blowfish-cfb,blowf...
>>
>> just change the server config.
>>
--
David Knight French
Black Mountain Computer Consulting
Voice: (858)279-4862
Email: [EMAIL PROTECTED]
