SSH Integration

[andrewpareles]

The default SSH Marketplace Extension is owned by Microsoft, so we need to add our own SSH integration.

This issue came up a few times before: #201 and #205.

[bjoaquinc]

@andrewpareles does this require creating a new extension using something like ssh2 that mimics the functionality of the default ssh extension microsoft owns?

[andrewpareles]

Yes

[bjoaquinc]

Alright so @andrewpareles @mathewpareles the focus is replicating the basic functionality of the Microsoft Remote-SSH extension by creating a new extension using ssh2. I made a streamlined list of the commands and settings we're going to keep. Feel free to update this or make recommendations:

---

Commands to Keep

• Add New SSH Host
  Essential for setting up new SSH configurations.

• Connect to Host
  Core functionality for establishing SSH connections.

• Open SSH Configuration File
  Allows users to modify their ~/.ssh/config file for advanced configurations.

• Show Logs
  Provides basic troubleshooting capabilities.

• Kill Local Connection Server for Host
  Useful for resolving connection issues.

---

Settings to Keep

• Remote.SSH: Config File
  Allows users to specify a custom SSH config file, essential for flexibility.

• Remote.SSH: Connect Timeout
  Ensures users can adjust connection timeouts for different environments.

• Remote.SSH: Path
  Lets users specify a custom SSH executable path, crucial for cross-platform support.

• Remote.SSH: Enable Agent Forwarding
  Useful for users needing to forward their SSH agent (e.g., for git or other tools).

• Remote.SSH: Enable X11 Forwarding
  Adds basic support for GUI forwarding over SSH, which is commonly needed.

• Remote.SSH: Log Level
  Enables debug or trace logging for troubleshooting.

• Remote.SSH: Max Reconnection Attempts
  Handles auto-reconnection attempts gracefully.

---

Features and Settings to Skip

• Advanced or Experimental Features (e.g., Enable Remote Command, Enable Dynamic Forwarding, Local Server Download, Use Exec Server, etc.).
• Settings for Port Forwarding or Custom Lockfile Locations (e.g., Default Forwarded Ports, Server Install Path, Lockfiles In Tmp).
• Platform-Specific or Niche Features (e.g., Suppress Windows SSH Warning, Use Flock, Server Pick Ports From Range).

---

Why This Selection?

The selected commands and settings ensure the ability to:

• Add and connect to SSH hosts.
• Modify and use custom configurations.
• Manage connection stability and agent forwarding.
• Troubleshoot with logging.

[bjoaquinc]

Found a potential alternative to Microsoft Remote-SSH extension called open-remote-ssh. I'll test it out and see how it needs to be adapted to fit Voids use case.

[bjoaquinc]

@andrewpareles I'm gonna need the void-server tarball to be accessible via a Github link/release, so that I can point Open Remote-SSH to it for downloading on the remote computer.

[andrewpareles]

@bjoaquinc You just want me to tarball this repo and make it into a release? https://github.com/voideditor/void-updates-server

[bjoaquinc]

@bjoaquinc You just want me to tarball this repo and make it into a release? https://github.com/voideditor/void-updates-server

The void-server tarball should be generated by the PR I made (voideditor/void-updates-server#1). The code is in server-package.sh. Making that tarball into a release would be perfect

[andrewpareles]

Ah got it! Looks great. Will build tonight, ETA tomorrow morning PT!

[andrewpareles]

@bjoaquinc added it here https://github.com/voideditor/void-updates-server/releases

It's all based on the updates-testing branch

Lmk if you need anything else!