Ciphers none error in sshd_config

From: John Doe (compsec3_at_hotmail.com)
Date: 07/14/03

  • Next message: Daniel Corbe: "Allow logins by username" 
    To: secureshell@securityfocus.com
Date: Mon, 14 Jul 2003 21:25:54 +0000

    All,

    I am using OpenSSH-3.6.1p1 on two Redhat 7.2 i386 machines.

    I am trying to transfer already encrypted files between machines. I don't
    want to re-encrypt the files but I do want to use ssh because of its strong
    authentication mechanisms (i.e. public key authentication). However, when I
    specify "Ciphers none" in my sshd_config file I get an error:

    Starting sshd:/etc/ssh/sshd_config line 12: Bad SSH2 cipher spec 'none'.

    I get the same error whether I specify Protocol 1 and or Protocol 2.

    Following advice from O'Reilly's book "SSH The Secure Shell, The Definitive
    Guide", I tried recompiling from source using:

    ./configure --with-none

    but it hasn't made any difference. In fact, "--with-none" isn't even listed
    as a configure option when I ran:

    ./configure --help

    My question then is this, has support for no encryption (i.e. Ciphers none)
    been eliminated from OpenSSH or am I doing something really stupid?

    James

    _________________________________________________________________
    Help STOP SPAM with the new MSN 8 and get 2 months FREE*
    http://join.msn.com/?page=features/junkmail

  • Next message: Daniel Corbe: "Allow logins by username"

    Relevant Pages

    • openssh with none algorithms
      ... openssh client to work with none ciphers, none mac. ... as "ssh -c none -m none user@host". ...
      (comp.security.ssh)
    • Why not Rijndael?
      ... I just wrote a short paper on SSH for one of my classes. ... list of supported ciphers in the Internet Draft for SSH 2.0 was very ... But the cipher that won the contest, Rijndael, is not supported by SSH ... If this is the new US standard, I should think it would be. ...
      (comp.security.ssh)