Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-50823

cannot add HostKeyAlgorithms to sshd_config

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • rhel-10.0.beta
    • openssh
    • No
    • None
    • rhel-sst-security-crypto
    • ssg_security
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • All
    • None

      What were you trying to do that didn't work?

      run TC /CoreOS/openssh/Regression/bz1360973-Support-of-HostKeyAlgorithms-for-sshd

      Please provide the package NVR for which bug is seen:

      /CoreOS/openssh/Regression/bz1360973-Support-of-HostKeyAlgorithms-for-sshd

      How reproducible:

      always

      Steps to reproduce

      1. run TC /CoreOS/openssh/Regression/bz1360973-Support-of-HostKeyAlgorithms-for-sshd
      2. add HostKeyAlgorithms to sshd_config (server or client)
      3. start sshd: runcon system_u:system_r:initrc_t:s0 bash -c "(/usr/sbin/sshd -ddd -f sshd_config -p 2222 &> ssh.log)&"
      4. start ssh connection: ssh -o "UserKnownHostsFile /dev/null" -i id_rsa root@localhost -p2222

      Expected results

      specified HostKeyAlgorithms are found in ssh.log

      TC PASS in all phases

      Actual results

      specified HostKeyAlgorithms are not present in ssh.log

      and

      sshd_config line 131: Bad key types 'ssh-ed25519,ssh-ed25519-cert-v01@openssh.com,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-rsa-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com'.

      TC failed in all phases

              dbelyavs@redhat.com Dmitry Belyavskiy
              rh-ee-mbezokon Miluse Bezo Konecna
              Dmitry Belyavskiy Dmitry Belyavskiy
              Miluse Bezo Konecna Miluse Bezo Konecna
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: