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

Fix password based ssh login issue #182

Merged
merged 2 commits into from
Feb 21, 2024
Merged

Fix password based ssh login issue #182

merged 2 commits into from
Feb 21, 2024

Conversation

jacobweinstock
Copy link
Member

Description

The previous sed command stopped working. The Ubuntu cloud image seems to write a different file for ssh settings now. This fixes the issue of ssh not allowing password based logins.

Why is this needed

Fixes: #

How Has This Been Tested?

How are existing users impacted? What migration steps/scripts do we need?

Checklist:

I have:

  • updated the documentation and/or roadmap (if required)
  • added unit or e2e tests
  • provided instructions on how to upgrade

The previous sed command wasnt working.
The new ubuntu cloud image seems to
write a different file for ssh settings.
This fixes the issue of ssh not allowing
password logins.

Signed-off-by: Jacob Weinstock <[email protected]>
@jacobweinstock jacobweinstock added the ready-to-merge Signal to Mergify to merge the PR. label Feb 21, 2024
@jacobweinstock jacobweinstock changed the title Fix password bases ssh login issue Fix password based ssh login issue Feb 21, 2024
@mergify mergify bot merged commit b4d7bf8 into main Feb 21, 2024
6 checks passed
@jacobweinstock jacobweinstock deleted the fix-ssh-issue branch February 21, 2024 14:55
ttwd80 pushed a commit to ttwd80/tinkerbell-playground that referenced this pull request Sep 7, 2024
## Description


The previous sed command stopped working. The Ubuntu cloud image seems to write a different file for ssh settings now. This fixes the issue of ssh not allowing password based logins.

## Why is this needed



Fixes: #

## How Has This Been Tested?





## How are existing users impacted? What migration steps/scripts do we need?





## Checklist:

I have:

- [ ] updated the documentation and/or roadmap (if required)
- [ ] added unit or e2e tests
- [ ] provided instructions on how to upgrade
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-to-merge Signal to Mergify to merge the PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants