Using stock OpenSSH 4.7 I found different behavior when trying to
specify the use of the 'none' cipher depending on the command line
option nomenclature. This is under linux 2.6.19-web100
using -ocipher=none
[root at delta openssh-4.7p1-hpnv19]# /home/rapier/ssh47/bin/scp -S
/home/rapier/ssh47/bin/ssh -ocipher=none -P 2222 ~rapier/2gb
rapier at localhost:/dev/null
rapier at localhost's password:
2gb
3% 74MB 32.7MB/s 01:00 ETA
using -cnone
[root at delta openssh-4.7p1-hpnv19]# /home/rapier/ssh47/bin/scp -S
/home/rapier/ssh47/bin/ssh -cnone -P 2222 ~rapier/2gb
rapier at localhost:/dev/null
No valid ciphers for protocol version 2 given, using defaults.
rapier at localhost's password:
2gb
1% 33MB 32.7MB/s 01:01 ETA
The difference being, of course, the warning given. In both cases the
behaviour is the same and results in a fall back to the default cipher.
Should this be made consistent?
Chris Rapier
On Wed, Sep 26, 2007 at 03:32:44PM -0400, Chris Rapier wrote:> Using stock OpenSSH 4.7 I found different behavior when trying to > specify the use of the 'none' cipher depending on the command line > option nomenclature. This is under linux 2.6.19-web100 > > using -ocipher=none > [root at delta openssh-4.7p1-hpnv19]# /home/rapier/ssh47/bin/scp -S > /home/rapier/ssh47/bin/ssh -ocipher=none -P 2222 ~rapier/2gb"Cipher" is an SSHv1-only directive so it will have no effect unless your connection is using Protocol 1. Try "Ciphers". -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.