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

Fixes #30121 - Generate SSH keys in PEM format #600

Merged
merged 1 commit into from
Jun 15, 2020

Conversation

adamruzicka
Copy link
Contributor

On EL8 the keys get generated in RFC4716 format which doesn't play well with the version of net-ssh we currently ship.

On EL8 the keys get generated in RFC4716 which doesn't play well with
the version of net-ssh we currently ship.
Copy link
Contributor

@wbclark wbclark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks @adamruzicka

@ehelms ehelms merged commit e74674d into theforeman:master Jun 15, 2020
@wbclark wbclark added Bug and removed Needs testing labels Jun 15, 2020
@ekohl
Copy link
Member

ekohl commented Jun 22, 2020

Could we have updated the net-ssh version or will we run into https://projects.theforeman.org/issues/30162 then?

@adamruzicka
Copy link
Contributor Author

Even the latest and greatest version of net-ssh considers all private keys beginning with -----BEGIN OPENSSH PRIVATE KEY----- to be ed25519 keys so that wouldn't help us at all here

@adamruzicka adamruzicka deleted the rex-pem branch June 22, 2020 09:19
@ekohl
Copy link
Member

ekohl commented Jun 22, 2020

But can't we ship the gems to support ed25519 as well or is that still a problem? That's probably more a packaging issue, but IMHO a good feature to support. Users might generate their own ed25519 keys and run into problems.

@adamruzicka
Copy link
Contributor Author

We could and we should, but that wouldn't change anything on the fact that net-ssh would still incorrectly detect the key type.

@ekohl
Copy link
Member

ekohl commented Jun 22, 2020

Ok, that sounds like a known issue we should document for REX users on EL8.

jhoblitt added a commit to lsst-it/lsst-control that referenced this pull request May 6, 2021
jhoblitt added a commit to lsst-it/lsst-control that referenced this pull request May 6, 2021
jhoblitt added a commit to lsst-it/lsst-control that referenced this pull request May 7, 2021
jhoblitt added a commit to lsst-it/lsst-control that referenced this pull request May 7, 2021
jhoblitt added a commit to lsst-it/lsst-control that referenced this pull request May 20, 2021
jhoblitt added a commit to lsst-it/lsst-control that referenced this pull request May 20, 2021
jhoblitt added a commit to lsst-it/lsst-control that referenced this pull request May 24, 2021
jhoblitt added a commit to lsst-it/lsst-control that referenced this pull request May 25, 2021
jhoblitt added a commit to lsst-it/lsst-control that referenced this pull request May 28, 2021
jhoblitt added a commit to lsst-it/lsst-control that referenced this pull request May 28, 2021
jhoblitt added a commit to lsst-it/lsst-control that referenced this pull request May 28, 2021
jhoblitt added a commit to lsst-it/lsst-control that referenced this pull request Jun 7, 2021
jhoblitt added a commit to lsst-it/lsst-control that referenced this pull request Jun 7, 2021
jhoblitt added a commit to lsst-it/lsst-control that referenced this pull request Jun 8, 2021
jhoblitt added a commit to lsst-it/lsst-control that referenced this pull request Jun 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants