Skip to content
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

SSH-RSA Keys broken after recent BOA update #1648

Open
ydnar79 opened this issue Apr 1, 2022 · 3 comments
Open

SSH-RSA Keys broken after recent BOA update #1648

ydnar79 opened this issue Apr 1, 2022 · 3 comments

Comments

@ydnar79
Copy link

ydnar79 commented Apr 1, 2022

I recently updated my BOA environment to release # 4.1.4-rel.

After successfully updating the system, the next time I attempted to SSH into the server, my root's SSH keys were refused.

Upon further investigation, I found that the issue is related to the included update of the OpenSSH server to release 8.8. As you can see by looking at these release notes: https://www.openssh.com/txt/release-8.8

This release disables RSA signatures using the SHA-1 hash algorithm
by default.

While I was able to regain access to the server using one of the newer and approved algorithms for OpenSSH 8.8. I then ran into an issue when I attempted to run the "barracuda up-stable" command.

ERROR: BOA requires working SSH (RSA) keys for system root present
ERROR: Please add and test your SSH (RSA) keys for root account
ERROR: before trying again

It appears that the current script does not take into account the use of the newer and more secure algorithms recommended by the updated OpenSSH software. While it does appear that it is technically possible to force the updated OpenSSH to use the older RSA key, it is highly discouraged according to their documentation.

Please make a note of this potential issue when performing the update process. (It can be a real pain to try and regain access to the system, especially without any sort of warning.)

It would also be ideal to have the script allow for other key types to be recognized as well so that it does not cause a potential block when updating. While also encouraging best security practices with newer and more advanced algorithms.

Thanks!

@alpha-omega-labs
Copy link

Confirming issue, after "system upgrade" unable to access root user with old key.

@omega8cc
Copy link
Owner

omega8cc commented May 8, 2023

Good point and also the reason we are back to changelog updates so people are aware of potentially problematic upgrades.

@graveguardian
Copy link

Have had this happen to me three times now...;-(

Any pointers on how I can regain access to my system?

Fresh install/upgrades on fresh Debian 11 vanilla.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants