[Bug 877] ssh 3.8.1p1 client cannot disable encryption with "-c none"

bugzilla-daemon at mindrot.org bugzilla-daemon at mindrot.org
Sun Jun 6 09:40:56 EST 2004


http://bugzilla.mindrot.org/show_bug.cgi?id=877

           Summary: ssh 3.8.1p1 client cannot disable encryption with "-c
                    none"
           Product: Portable OpenSSH
           Version: 3.8.1p1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ssh
        AssignedTo: openssh-bugs at mindrot.org
        ReportedBy: mohit_aron at hotmail.com


I'm using an ssh 3.8.1p1 client on my home machine to connect to my an sshd
3.6.1p2 server on my office machine. Since I'm connecting over a VPN connection,
I have no need for encryption. However, since my office machine does not run
telnet/rlogin server, I can only connect to it using ssh. Thus, I need to turn off
encryption while connecting. It seems I'm not able to do this with the '-c none'
option. Here's the error I get when I run 'ssh -c none' to my office machine:
   No valid ciphers for protocol version 2 given, using defaults.

The /etc/ssh/sshd_config file on my office machine does contain the following 
line:
   Ciphers aes128-cbc,blowfish-cbc,3des-cbc,cast128-cbc,none2

However, the ssh 3.8.1p1 client doesn't seem to recognize the cipher 'none2'.
This is confirmed by looking at the openssh source in the file cipher.c. 
There is no cipher called "none2" in 3.8.1p1 source while it exists in 
3.6.1p2 source.

So I guess there are two problems:
      (1) ssh 3.8.1p1 client isn't able to disable encryption when talking to 
          a 3.6.1p2 sshd which allows the none2 cipher.
      (2) The man page for ssh 3.8.1p1 doesn't indicate an option '-c none' 
          while the man page for ssh 3.6.1p2 does. I hope the ability to 
          open an unencrypted ssh channel hasn't been removed by the developers
          in the later version of ssh.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.




More information about the openssh-bugs mailing list