Skip to content

Remove insecure legacy SSH key workaround #415

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.

Sign up for GitHub

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

Open
astehlik wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Remove insecure legacy SSH key workaround #415

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 0 additions & 24 deletions Documentation/Troubleshooting/Index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,30 +109,6 @@ connections to `review.typo3.org`:

Now the connection should work without having to specify any parameters as described above.

If this does not work another issue might be that your SSH version is too new and does not
accept the signature algorithm. You can test this by executing:

.. code-block:: bash
:caption: shell command

ssh -v -p 29418 -i <path-to-private-key> <username>@review.typo3.org 2>&1 | grep "no mutual signature algorithm"

If you see the following:

.. code-block:: none
:caption: result

debug1: send_pubkey_test: no mutual signature algorithm

you need to allow the rsa Algorithm in your SSH config:

.. code-block:: text
:caption: ~/.ssh/config

Host review.typo3.org
...
PubkeyAcceptedKeyTypes +ssh-rsa

Push: invalid committer
-----------------------

Expand Down