faq: add entry that explains SSH crypto change in F33 #220
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jlebon
approved these changes
Dec 17, 2020
modules/ROOT/pages/faq.adoc
Outdated
| @@ -336,3 +336,44 @@ systemd: | |||
|
|
|||
| For more information see | |||
| https://github.com/coreos/fedora-coreos-tracker/issues/519[the tracker issue discussion]. | |||
|
|
|||
| == After the rebase to Fedora 33 why does my tooling that uses SSH cease to work? | |||
There was a problem hiding this comment.
How about something simpler like
Suggested change
| == After the rebase to Fedora 33 why does my tooling that uses SSH cease to work? | |
| == Why does SSH stop working after upgrading to Fedora 33? |
?
modules/ROOT/pages/faq.adoc
Outdated
Comment on lines
353
to
355
| For example, GoLang has an https://github.com/golang/go/issues/37278[open issue] | ||
| to solve this problem in the GoLang stack, but has yet to resolve the | ||
| issue. This has been hit and worked around by the FCOS community in |
There was a problem hiding this comment.
Suggested change
| For example, GoLang has an https://github.com/golang/go/issues/37278[open issue] | |
| to solve this problem in the GoLang stack, but has yet to resolve the | |
| issue. This has been hit and worked around by the FCOS community in | |
| For example, Go has an https://github.com/golang/go/issues/37278[open issue] | |
| to solve this problem in its SSH implementation, but has yet to resolve | |
| it. This has been hit and worked around by the FCOS community in |
?
modules/ROOT/pages/faq.adoc
Outdated
| - https://github.com/coreos/fedora-coreos-tracker/issues/699[coreos/fedora-coreos-tracker#699] | ||
| - https://github.com/coreos/coreos-assembler/issues/1772[coreos/coreos-assembler#1772] | ||
|
|
||
| If you run into this problem and need to workaround the issue you |
There was a problem hiding this comment.
Suggested change
| If you run into this problem and need to workaround the issue you | |
| If you run into this problem and need to work around the issue, you |
| If you run into this problem and need to workaround the issue you | ||
| have a few options: | ||
|
|
||
| - Switch to a newer non-RSA key type. |
There was a problem hiding this comment.
Suggested change
| - Switch to a newer non-RSA key type. | |
| - Switch to a newer non-RSA SHA-1 key type. |
(RSA SHA-2 works, right?)
There was a problem hiding this comment.
The RSA SHA2 keyex algo works, but using a non RSA key itself will workaround the problem entirely, which is what I'm trying to say here.
dustymabe
force-pushed
the
dusty-ssh-keys
branch
from
4830666 to
c8e54c2
Compare
|
Implemented most of your suggested changes! Thanks for the review. |
bgilbert
reviewed
Dec 17, 2020
| You may hit issues if you use RSA keys and: | ||
|
|
||
| * use an old version of the `SSH` client | ||
| * use tooling/software libraries that don't support using RSA SHA2 host key signatures |
There was a problem hiding this comment.
"public key signatures" would be clearer, since host keys aren't involved here.
There was a problem hiding this comment.
thanks for the suggestion. Fix in #222
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.