fix(ssh): Ensure that the private key ends with a newline character

[GT-610]

Resolve #499.

Fixes an issue where SSH private key files were not written with a newline character at the end, preventing parsing errors in certain SSH clients

Update the package

Summary by CodeRabbit

• Bug Fixes
  • Generated SSH private keys now include a trailing newline and are saved with secure file permissions on non-Windows systems.
• Behavior
  • SSH invocation now handles additional command arguments in the correct order to improve connection reliability.
• Chores
  • Updated a subproject reference with no user-facing API changes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 6bc42c47-91b3-4957-bef6-97f123a32a63

📥 Commits

Reviewing files that changed from the base of the PR and between 7c7b863 and 2b835ae.

📒 Files selected for processing (2)

• lib/view/widget/server_func_btns.dart
• packages/computer

✅ Files skipped from review due to trivial changes (1)

• packages/computer

🚧 Files skipped from review as they are similar to previous changes (1)

• lib/view/widget/server_func_btns.dart

---

📝 Walkthrough

Walkthrough

The changes update SSH-related behavior in lib/view/widget/server_func_btns.dart: when generating a private key file the code ensures the key content ends with a trailing newline and sets file permissions to 0600 on non-Windows platforms after writing. SSH command assembly is modified to place user@host at the end of the argument list (['ssh'] + extraArgs + ['user@host']). Minor whitespace edits and a submodule commit addition for packages/computer were also included.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Out of Scope Changes check	⚠️ Warning	The SSH command parameter reordering change is not directly related to the primary objective of ensuring trailing newlines in private keys and may introduce unintended behavioral changes.	Clarify whether the SSH command parameter reordering is necessary for the key parsing fix or if it should be addressed separately.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: ensuring private keys end with a newline character, which directly addresses the issue of SSH key parsing failures.
Linked Issues check	✅ Passed	The code changes add trailing newline to private keys and set file permissions on non-Windows platforms, directly addressing the SSH key parsing error reported in issue #499.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.