Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
I have attempted on multiple boxes to create a dsa key to provide simple trusted ssh access between my cluster nodes. It is being rejected. Is it deprecated ? rsa works fine.
Version-Release number of selected component (if applicable):
RHEL-8.0-20181120.0
How reproducible:
every time
Steps to Reproduce:
[root@pats .ssh]# ssh-keygen -t dsa
Generating public/private dsa key pair.
Enter file in which to save the key (/root/.ssh/id_dsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_dsa.
Your public key has been saved in /root/.ssh/id_dsa.pub.
The key fingerprint is:
SHA256:3+8jYRu0fBnACuo+DDuiCZ+Lh8idaB3OcNdpKSh5OdM root.lab.eng.bos.redhat.com
The key's randomart image is:
+---[DSA 1024]----+
| . |
| . o |
| . . . . |
| . . . . |
| . +.. S o . o |
| + O.E.= . .* o |
|+.@ *=o ...= |
|+BoBo + o.. |
|=o+o . . oo. |
+----[SHA256]-----+
[root@pats .ssh]# ls -l
total 12
-rw-------. 1 root root 1413 Mar 11 11:53 id_dsa
-rw-r--r--. 1 root root 627 Mar 11 11:53 id_dsa.pub
-rw-r--r--. 1 root root 179 Mar 11 11:51 known_hosts
[root@pats .ssh]# ssh `hostname`
The authenticity of host 'pats.perf.lab.eng.bos.redhat.com (10.16.28.106)' can't be established.
ECDSA key fingerprint is SHA256:uFLtiB/zfGAB8xrDII3fi9QfZjN80NvoOOK6OpYmt4M.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'pats.perf.lab.eng.bos.redhat.com,10.16.28.106' (ECDSA) to the list of known hosts.
root.lab.eng.bos.redhat.com's password:
Activate the web console with: systemctl enable --now cockpit.socket
Last login: Tue Mar 5 13:36:16 2019 from 10.18.81.20
[root@pats ~]# logout
[root@pats .ssh]# cat id_dsa.pub > authorized_keys
[root@pats .ssh]# ssh `hostname`
root.lab.eng.bos.redhat.com's password:
Actual results:
asks for password
Expected results:
should just log in.
Additional info: