"cipher none" alternatives ?

[Christopher Linn]

On Sat, Mar 17, 2001 at 06:24:38AM -0800, Dan Kaminsky wrote:
> > > You've not done Arcfour with OpenSSH; it's not supported.  I'm not
> > > sure if I like that or not.
> > 
> > It is supported for ssh2. ssh -2 -oCiphers=arcfour ...
> 
> dankamin at CISCO-CD5ZTDFXI ~
> $ ssh -h
> ...
> -c cipher  Select encryption algorithm:  ``3des'', ``blowfish''
> 
> Self-Documentation trumps--can be a blessing or a curse.

perhaps the manpage is more current than the embedded help msg?

from ssh(1):

[...]
     -c cipher_spec
             Additionally, for protocol version 2 a comma-separated list of
             ciphers can be specified in order of preference.  See Ciphers for
             more information.
[...]
     Ciphers
             Specifies the ciphers allowed for protocol version 2 in order of
             preference.  Multiple ciphers must be comma-separated.  The de-
             fault is

               ``3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes128-cbc,
                 aes192-cbc,aes256-cbc,rijndael128-cbc,rijndael192-cbc,
                 rijndael256-cbc,rijndael-cbc at lysator.liu.se''
[...]

> --Dan

chris

-- 
Christopher Linn, <celinn at mtu.edu>    | By no means shall either the CEC
Staff System Administrator            | or MTU be held in any way liable
  Center for Experimental Computation | for any opinions or conjecture I
    Michigan Technological University | hold to or imply to hold herein.