Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Remote Execution fails when RHEL 8.2 clients are configured with the DEFAULT:NO-SHA1 systemwide crypto policy
Version-Release number of selected component (if applicable):
satellite-6.8.0-1.el7sat.noarch
crypto-policies-20191128-2.git23e1bf1.el8.noarch
How reproducible:
Every time
Steps to Reproduce:
1. Configure the NO-SHA1 crypto policy on a RHEL 8.2 client:
update-crypto-policies --set DEFAULT:NO-SHA1
2. From Satellite, copy foreman-proxy SSH keys to the client:
ssh-copy-id -i ~foreman-proxy/.ssh/id_rsa_foreman_proxy.pub user.xx.xx
3. Verify SSH works:
ssh -i ~foreman-proxy/.ssh/id_rsa_foreman_proxy user.xx.xx
4. Schedule a remote execution job from Satellite:
All hosts -> select host -> Schedule remote job
Job Category: Commands
Job template: Run Command - SSH Default
Command: hostname
Actual results:
Remote job fails
Expected results:
Remote job succeeds
Additional info:
Satellite reports the following in /var/log/foreman/production.log:
Parameters: {"callback"=>{"task_id"=>"f11391f0-e310-49bc-8ffa-7497e0b1cd38", "step_id"=>3}, "data"=>{"result"=>[{"output_type"=>"
debug", "output"=>"Error initializing command: Net::SSH::AuthenticationFailed - Authentication failed for user user.xx.xx", "timestamp"=>1604018256.3824
368}], "runner_id"=>"a82ae4db-f852-4790-8fa0-fed85c65e610", "exit_status"=>"EXCEPTION"}, "task"=>{}}
The client reports the following in /var/log/secure:
sshd[8898]: userauth_pubkey: key type ssh-rsa not in PubkeyAcceptedKeyTypes [preauth]
Disabling the NO-SHA1 policy enables remote execution to proceed:
update-crypto-policies --set DEFAULT
systemctl restart sshd
Looks like the support for using rsa-sha2-256 and rsa-sha2-512 as PubkeyAcceptedKeyTypes is a bit wonky in the ssh library we use. I managed to reproduce the issue even with its latest version even though it should be fully supported there. Revived the issue there https://github.com/net-ssh/net-ssh/issues/712#issuecomment-720403946
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2022:5498
Description of problem: Remote Execution fails when RHEL 8.2 clients are configured with the DEFAULT:NO-SHA1 systemwide crypto policy Version-Release number of selected component (if applicable): satellite-6.8.0-1.el7sat.noarch crypto-policies-20191128-2.git23e1bf1.el8.noarch How reproducible: Every time Steps to Reproduce: 1. Configure the NO-SHA1 crypto policy on a RHEL 8.2 client: update-crypto-policies --set DEFAULT:NO-SHA1 2. From Satellite, copy foreman-proxy SSH keys to the client: ssh-copy-id -i ~foreman-proxy/.ssh/id_rsa_foreman_proxy.pub user.xx.xx 3. Verify SSH works: ssh -i ~foreman-proxy/.ssh/id_rsa_foreman_proxy user.xx.xx 4. Schedule a remote execution job from Satellite: All hosts -> select host -> Schedule remote job Job Category: Commands Job template: Run Command - SSH Default Command: hostname Actual results: Remote job fails Expected results: Remote job succeeds Additional info: Satellite reports the following in /var/log/foreman/production.log: Parameters: {"callback"=>{"task_id"=>"f11391f0-e310-49bc-8ffa-7497e0b1cd38", "step_id"=>3}, "data"=>{"result"=>[{"output_type"=>" debug", "output"=>"Error initializing command: Net::SSH::AuthenticationFailed - Authentication failed for user user.xx.xx", "timestamp"=>1604018256.3824 368}], "runner_id"=>"a82ae4db-f852-4790-8fa0-fed85c65e610", "exit_status"=>"EXCEPTION"}, "task"=>{}} The client reports the following in /var/log/secure: sshd[8898]: userauth_pubkey: key type ssh-rsa not in PubkeyAcceptedKeyTypes [preauth] Disabling the NO-SHA1 policy enables remote execution to proceed: update-crypto-policies --set DEFAULT systemctl restart sshd