mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lyor Goldstein (Jira)" <j...@apache.org>
Subject [jira] [Commented] (SSHD-1118) Unable to connect with Fedora 33 which has dropped ssh-rsa from PubkeyAcceptedKeyTypes
Date Fri, 15 Jan 2021 09:24:00 GMT

    [ https://issues.apache.org/jira/browse/SSHD-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17265853#comment-17265853

Lyor Goldstein commented on SSHD-1118:

{quote}I guess we don't insist on it, but it means users have to regenerate their keys that
were working.
This is true - however, bear in mind that this is prevailing recommendation in the security
community - so the sooner the better. Note that this affects not only SSH but also TLS - many
TLS libraries are deprecating and/or deleting RSA support entirely.
{quote}better if we if we can find anything to keep existing keys working
I agree, but I don't see how this is a MINA SSHD issue - by the very description of the problem
it is a Fedora issue. FYI, our code still supports RSA - client and server (as of 2.6.0 the
support is still there but must be activated +explicitly+) so I am at a loss as to how we
can help here.

> Unable to connect with Fedora 33 which has dropped ssh-rsa from PubkeyAcceptedKeyTypes
> --------------------------------------------------------------------------------------
>                 Key: SSHD-1118
>                 URL: https://issues.apache.org/jira/browse/SSHD-1118
>             Project: MINA SSHD
>          Issue Type: Bug
>    Affects Versions: 2.4.0
>            Reporter: Ian Wienand
>            Priority: Major
> This problem was noted with Gerrit using a 2.4.0 mina sshd server [1] after a recent
upgrade.  Some users using Fedora 33 started being not able to log in.
> It turns out that Fedora >=33 has dropped rsa-ssh from it's default {{PubkeyAcceptedKeyTypes}}
in {{/etc/crypto-policies/back-ends/openssh.config}}.  You either have to modify your policy
globally to "legacy" with "update-crypto-policies" or manually set {{PubkeyAcceptedKeyTypes=ssh-rsa}}
for failing servers.
> I understand that {{server-sig-algs}} support isn't fully implemented in mina sshd as
yet, so the client will not be seeing the negotiation list.
> However, it seems rsa-sha2-256/512 are supported?  It seems like forcing this with {{ssh
-oPubkeyAcceptedKeyTypes=rsa-sha2-512}} should work, but it does not (see related gerrit bug)?
> I can provide ssh connect logs, etc. if it will help; at this point I think it's mostly
about understanding Fedora's change and any mina limitations so we can find the best solution
for users.  Although Fedora 33 users are obviously a small minority now, it probably flags
something other distros will take up sooner or later.
> Thanks!
>  [1] [https://bugs.chromium.org/p/gerrit/issues/detail?id=13930]

This message was sent by Atlassian Jira

To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For additional commands, e-mail: dev-help@mina.apache.org

View raw message