We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
termbot is a great piece of code that allows SSH on a phone with a Yubikey 5C (RSA4096, no ed255519 for or KDF support for now).
termbot is able to cope with the latest recommendations like:
But on the cipher side it seems to be stuck to an older implementation with only aes256-ctr or less. I couldn't get for example chacha20-poly1305@openssh.com or aes256-gcm@openssh.com to be accepted.
Is there a plan to support those standards that are now enabled by default on a lot of OpenSSH configurations?
The text was updated successfully, but these errors were encountered:
While this wasn't your main request: Ed25519 and KDF support is now supported. Regarding the symmetric ciphers, I am following upstream ConnectBot.
Sorry, something went wrong.
This is a great addition that makes hardware dongles even more versatile.
No branches or pull requests
termbot is a great piece of code that allows SSH on a phone with a Yubikey 5C (RSA4096, no ed255519 for or KDF support for now).
termbot is able to cope with the latest recommendations like:
But on the cipher side it seems to be stuck to an older implementation with only aes256-ctr or less.
I couldn't get for example chacha20-poly1305@openssh.com or aes256-gcm@openssh.com to be accepted.
Is there a plan to support those standards that are now enabled by default on a lot of OpenSSH configurations?
The text was updated successfully, but these errors were encountered: