From: Efraim Flashner <efraim@flashner.co.il>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: 44887@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: bug#44887: openssh service creates DSA keys
Date: Wed, 19 Jun 2024 15:02:04 +0300 [thread overview]
Message-ID: <ZnLIvD7i4_SGsjB7@3900XT> (raw)
In-Reply-To: <CAEwRq=rU2wD7ZzcjnTJ0+1DAP6TVE+aytqCKxCbLg0KRjnqn9Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2695 bytes --]
On Tue, Jun 18, 2024 at 07:28:35PM +0000, Vincent Legoll wrote:
> Hello,
>
> I've done some digging on that issue. Hope it'll help.
>
> It looks like the clients still support the DSA keys.
>
> This is on a Void linux desktop:
>
> [vince@destop ~]$ ssh -Q PubkeyAcceptedAlgorithms | grep -i dss
> ssh-dss
> ssh-dss-cert-v01@openssh.com
>
> The following Guix VM has been created 2 days ago, with a very light config
>
> vince@guix ~$ ssh -Q PubkeyAcceptedAlgorithms | grep -i ssh-dss
> ssh-dss
> ssh-dss-cert-v01@openssh.com
>
> So, I created a DSA PKI key pair, like so:
>
> ssh-keygen -N '' -t dsa -f ssh-key-dsa
>
> Uploaded the public key to the guix VM, as ~vince/.ssh/authorized_keys
> then tried to connect to the OpenSSH server on that VM
>
> [vince@desktop ~]$ ssh -vi ssh-key-dsa vince@10.0.0.101
> OpenSSH_9.7p1, OpenSSL 3.3.0 9 Apr 2024
> debug1: Reading configuration data /home/vince/.ssh/config
> debug1: /home/vince/.ssh/config line 1: Applying options for *
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: Connecting to 10.0.0.101 [10.0.0.101] port 22.
> debug1: Connection established.
> debug1: identity file ssh-key-dsa type 1
> [...]
> debug1: Skipping ssh-dss key ssh-key-dsa - corresponding algorithm not
> in PubkeyAcceptedAlgorithms
> debug1: No more authentication methods to try.
> vince@10.0.0.101: Permission denied (publickey).
>
> So it looks like DSA client keys are not accepted any more by default.
>
> Is there a problem for the server host key ?
>
> vince@guix ~$ ls /etc/ssh/
> authorized_keys.d/ ssh_host_ed25519_key ssh_host_rsa_key.pub
> ssh_host_ecdsa_key ssh_host_ed25519_key.pub
> ssh_host_ecdsa_key.pub ssh_host_rsa_key
>
> No DSA keys here. Maybe something has been changed and they are not
> created any more.
>
> So I'm not sure there is a problem, or am I mistaken ?
> Didn't I look hard enough ?
>
> WDYT ?
>
> Announce of DSA support removal from OpenSSH:
> https://lists.mindrot.org/pipermail/openssh-unix-dev/2024-January/041132.html
>
> Some context about DSA keys:
> https://security.stackexchange.com/questions/112802/why-openssh-deprecated-dsa-keys
It looks like openssh, at some point in the past <period-of-time>,
stopped creating host DSA keys by default. Given the original bug report
was that DSA keys were created by default and now they're not I think we
can close this bug now.
Any objections?
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-06-19 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 15:14 bug#44887: openssh service creates DSA keys Efraim Flashner
2024-06-18 19:28 ` Vincent Legoll
2024-06-19 12:02 ` Efraim Flashner [this message]
2024-06-19 17:18 ` Vincent Legoll
2024-06-19 20:10 ` Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZnLIvD7i4_SGsjB7@3900XT \
--to=efraim@flashner.co.il \
--cc=44887@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=vincent.legoll@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).