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

Locked out of new install; Can't login to server #1777

Closed
graveguardian opened this issue Mar 27, 2024 · 5 comments
Closed

Locked out of new install; Can't login to server #1777

graveguardian opened this issue Mar 27, 2024 · 5 comments

Comments

@graveguardian
Copy link

Found this issue (SSH-RSA Keys broken after recent BOA update #1648) after being locked out of three successful installs... ;-(

As I'm on an unmanaged server, my hosting company isn't being much help...just telling me that SSH is locking me out.

How can I regain access to my server. The aegir system itself is accessible, but can't login to server.

@graveguardian
Copy link
Author

In reading the SSH release doc, it states:

"Incompatibility is more likely when connecting to older SSH
implementations that have not been upgraded or have not closely tracked
improvements in the SSH protocol. For these cases, it may be necessary
to selectively re-enable RSA/SHA1 to allow connection and/or user
authentication via the HostkeyAlgorithms and PubkeyAcceptedAlgorithms
options. For example, the following stanza in ~/.ssh/config will enable
RSA/SHA1 for host and user authentication for a single destination host:

Host old-host
    HostkeyAlgorithms +ssh-rsa

PubkeyAcceptedAlgorithms +ssh-rsa

We recommend enabling RSA/SHA1 only as a stopgap measure until legacy
implementations can be upgraded or reconfigured with another key type
(such as ECDSA or Ed25519)."

So, if I understand this correctly, I need to modify ~/.ssh/config to add those lines, correct? How do I do that if I can't log in to the server? Via VNC from within my account on my host?

Thanks for any direction!

@omega8cc
Copy link
Owner

omega8cc commented Apr 3, 2024

Have you added your SSH keys on the server as explained in the docs before running installation?

@graveguardian
Copy link
Author

graveguardian commented Apr 3, 2024 via email

@omega8cc
Copy link
Owner

omega8cc commented Apr 3, 2024

Perhaps you have too old OpenSSH version installed locally? Try to upgrade and generate new SSH keys to make sure, I don't see any other reason why you would be locked. Also, make sure to read:

* Once OpenSSH is installed on barracuda upgrade, the server keys will change,

@graveguardian
Copy link
Author

graveguardian commented Apr 3, 2024 via email

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

2 participants