mirror of
https://github.com/xpipe-io/xpipe.git
synced 2024-12-01 12:00:31 +00:00
60 lines
5 KiB
Markdown
60 lines
5 KiB
Markdown
|
## Coherent desktops
|
||
|
|
|
||
|
|
XPipe now comes with support for remote desktop connections. VNC connections are fully handled over SSH and can therefore be established on top of any existing SSH connection you have in XPipe. RDP support is realized similar to the terminal support, i.e. by launching your preferred RDP client with the connection information. X11-forwarding for SSH is also now supported.
|
||
|
|
|
||
|
|
With support for remote graphical desktop connection methods as well now in XPipe 9, the big picture idea is to implement the concept of coherent desktops. Essentially, you can launch predefined desktop applications, terminals, and scripts on any remote desktop connection, regardless of the underlying connection implementation. In combination with the improved SSH tunnel and background session support, you can launch graphical remote applications with one click in the same unified way for VNC over SSH connections, RDP connections, and X11-forwarded SSH connections.
|
||
|
|
|
||
|
|
The general implementation and concept will be refined over the next updates.
|
||
|
|
|
||
|
|
## SSH connection improvements
|
||
|
|
|
||
|
|
- Tunneled and X11-forwarded custom SSH connections are now properly detected and can be toggled on and off to run in the background as normal tunnels. This applies to normal connections and also SSH configs
|
||
|
|
|
||
|
|
- The connection establishment has been reworked to reduce the amount of double prompts, e.g. for smartcards or 2FA, where user input is required twice.
|
||
|
|
|
||
|
|
- The custom SSH connections now properly apply all configuration options of your user configuration file. They also now correctly apply multiple options for the same key correctly.
|
||
|
|
|
||
|
|
- Any value specified for the `RemoteCommand` config option will now be properly applied when launching a terminal. This allows you to still use your preexisting init command setup, e.g. with tmux.
|
||
|
|
|
||
|
|
- There is now support defining multiple host entries in place in a custom SSH connection. This is useful for cases where you want to use ProxyJump hosts in place without having to define them elsewhere.
|
||
|
|
|
||
|
|
- A host key acceptance notification is now displayed properly in case your system doesn't automatically accept new host keys
|
||
|
|
|
||
|
|
## SSH for unknown shells (Professional feature)
|
||
|
|
|
||
|
|
There's now an option to not let XPipe interact with the system. In case a system that does not run a known command shell, e.g. a router, link, or some IOT device, XPipe was previously unable to detect the shell type and errored out after some time. This option fixes this problem. This feature is available in the professional edition preview for two weeks.
|
||
|
|
|
||
|
|
## SSH X11 Forwarding on Windows via WSL
|
||
|
|
|
||
|
|
You can now enable X11 forwarding for an SSH connection.
|
||
|
|
|
||
|
|
XPipe allows you to use the WSL2 X11 capabilities on Windows for your SSH connection. The only thing you need for this is a [WSL2](https://learn.microsoft.com/en-us/windows/wsl/install) distribution installed on your local system. XPipe it will automatically choose a compatible installed distribution if possible, but you can also use another one in the settings menu.
|
||
|
|
|
||
|
|
This means that you don't need to install a separate X11 server on Windows. However, if you are using one anyway, XPipe will detect that and use the currently running X11 server.
|
||
|
|
|
||
|
|
## Translations
|
||
|
|
|
||
|
|
XPipe 9 now comes with translations for the user interface. These were initially generated with DeepL and can be easily improved and corrected by anyone on GitHub. You can check them out in action and if there is any translation you don't like, submit a quick pull request to fix it. For instructions on how to do this, see https://github.com/xpipe-io/xpipe/tree/master/lang.
|
||
|
|
|
||
|
|
## Terminal improvements
|
||
|
|
|
||
|
|
The terminal integrations have been reworked across the board. To better show which terminals are well supported and which aren't, there is now a status indicator for every available terminal. This will show you how good the XPipe integration with each one is and which terminals are recommended to be used with XPipe.
|
||
|
|
|
||
|
|
The kitty terminal is now fully supported with tabs on both Linux and macOS. The Warp terminal integration now correctly enables all Warp features on remote shells. On macOS, other third-party prompts also now work properly in the launched terminals.
|
||
|
|
|
||
|
|
## Password manager improvements
|
||
|
|
|
||
|
|
The password manager handling has been improved and some potential sources of errors and confusion have been eliminated. There are also now a few command templates available for established password managers to quickly get started.
|
||
|
|
|
||
|
|
## Improved keyboard control
|
||
|
|
|
||
|
|
It is a goal to be able to use XPipe only with a keyboard either for productivity or for accessibility reasons. XPipe 9 introduces improved keyboard support with new shortcuts and improved focus control for navigating with the arrow keys, tab, space, and enter.
|
||
|
|
|
||
|
|
## Improved logo
|
||
|
|
|
||
|
|
The application logo has been improved with of regards to contrast and visibility, which often was a problem on dark backgrounds. It should now stand out on any background color.
|
||
|
|
|
||
|
|
## Other changes
|
||
|
|
|
||
|
|
There have been countless small bug fixes across the board. They are not listed individually here, but hopefully you will notice some of them.
|