-
Notifications
You must be signed in to change notification settings - Fork 393
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keepass2Android uses SSH-RSA which is no longer allowed by default #1812
Comments
I am having this same issue. May I suggest switching to ed25519? Much more secure and won't be phased out for quite some time. |
note to myself: ed25519 doesn't seem to be supported by JSch at the moment (https://sourceforge.net/p/jsch/feature-requests/7/), but some forks seem to support it (subhra74/snowflake#16) |
Same issue here. Another solution would be SHA2. This wouldn't even need new keys, just an updated SSH client with SHA2 support. |
I have the same issue, also applied the workaround. Is there any progress with this issue? |
Is there an update for this? I want to remove the RSA workaround from my server, but I still have clients using Keepass2Android. Not here to rush, just wondering what the status of this is. |
looking at https://sourceforge.net/p/jsch/feature-requests/7/ I don't see an update in JSch |
@PhilippC Thanks for the great app, sorry jsch has been a thorn; it looks like jsch is not being maintained, and the fork you listed above isn't maintained either. For people with very dated ssh servers... Could have a checkbox for legacy ssh settings to cover old + current ssh servers? ( https://github.com/mwiede/jsch/wiki/Jsch-Configuration ) Though I'd be happy just with modern settings/interop... :) |
Ubuntu 22.04 now ships with an sshd version that disallows ssh-rsa by default. The workaround in the first post works fine. |
com.jcraft:jsch is not actively maintained anymore and lacks support for modern public key algorithms such as rsa-sha2-256. It only supports ssh-rsa which is disabled in up-to-date environments. com.github.mwiede:jsch was created as a drop-in replacement which works in modern environments [1]. Sources are taken from maven central [2]. The following files were omitted, because they depend on additional 3rd-party libraries which we do not have / do not need: com/jcraft/jsch/JUnixSocketFactory.java com/jcraft/jsch/Log4j2Logger.java com/jcraft/jsch/PageantConnector.java com/jcraft/jsch/Slf4jLogger.java com/jcraft/jsch/SSHAgentConnector.java com/jcraft/jsch/bc/* com/jcraft/jsch/jgss/GSSContextKrb5.java Fixes PhilippC#1812. [1] https://github.com/mwiede/jsch [2] https://repo1.maven.org/maven2/com/github/mwiede/jsch/0.2.5/jsch-0.2.5-sources.jar
I try to use public key authentication to connect to my Linux server via SFTP but recently it has not worked. The SSH logs show this:
I have no option to change the public key or which algorithm keepass2android gives to me. Can this be changed to a more secuer algorithm or an ability to choose my own public key? This issue is also documented here https://bbs.archlinux.org/viewtopic.php?id=270005 which indicates sshd was changed recently to no longer allow ssh-rsa by default.
Workaround currently in place:
Setting SSHD to accept ssh-rsa. Adding the following lines of code to /etc/ssh/sshd and then restarting sshd works.
The text was updated successfully, but these errors were encountered: