AWS support
You can now connect to your AWS systems from within XPipe. Currently, EC2 systems and S3 buckets are supported. The integration works on top of the AWS CLI, meaning that it is required to be installed on your system. The usage of the AWS CLI allows the integration to work very flexibly on any existing CLI setup if you already use the CLI. You can use any IAM access keys and authentication methods with it.
The EC2 support works as with any other remote system in XPipe. The connections can be established via the SSH with optional AWS Systems Manager (SSM) support. The SSM support allows you to also reach systems that do not have a security group configured to allow external access to the normal SSH port.
The S3 support is available both for AWS buckets and other external buckets that are compatible with the S3 protocol. More enhancements to the performance and features of s3 file systems are planned.
SSH keys
You can now generate new SSH keys from within XPipe. The keys are generated via the OpenSSH ssh-keygen CLI tool, so you can be assured that the keys are generated in a cryptographically secure manner. You can generate keys with this button:
This keygen supports RSA, ED25519, and ED25519 + FIDO2:
Keys of identities can now also be automatically applied to systems, allowing you to perform a quick key rotation when needed:
The process of changing the authentication configuration of a system is not always one simple step. So the dialog is a comprehensive overview of what is needed to apply a certain identity to a remote system, with various quick-action buttons and notes. This gives you still full manual control of what should be done and an overview what is required prior to doing so.
As adding new authorized identities to systems requires the public key, there is now the functionality to generate and store the public key for identities based on the existing private key:
Tags
You can now create and add tags to connection entries. This allows you to have a more structured workflow when filtering individual connections.
SSH jump servers
The jump server / gateway configuration has been reworked to make the configuration more intuitive. You can now control the jump server behaviour right at the gateway field for a connection. When a gateway is set, XPipe now defaults to using it as a jump server unless the option is explicitly disabled, which is a change from the previous version where it was the other way around.
Tailscale
The tailscale integration has been updated with the recent improvements that were implemented for Netbird and AWS. It no longer requires the Tailscale SSH auth and instead gives you the option to use the automatic Tailscale SSH auth or connect normally to an SSH server, which requires password / key authentication. When configuring a tailscale system, you can choose the authentication type.
Furthermore, you can now use Tailscale connection entries as the base for other types of connections, e.g. direct RDP / VNC connections.
Split terminals
There is now a new batch action to open multiple systems in a split terminal pane instead of individual tabs. This action is only supported for terminals that support this, which currently includes: Windows Terminal, Kitty, and WezTerm. In addition, this is also supported when using any other terminal and a terminal multiplexer like tmux or zellij.
This allows you to also use a feature like broadcast mode of your terminal to type one command into multiple terminal panes at the same time.
Group vaults
In addition to existing team vaults with multiple users, you can now also set up team group vaults:
They work basically the same as user vaults, only the authentication/unlock workflow differs. Each group has a shared group secret, which can automatically be retrieved in one of multiple ways. This gives organization administrators the ability to control access to connections from a central location without users having to supply any passwords. You can flexibly convert existing team vaults into group vaults if needed.
Other
- The entire interface has been reworked to better work with screen readers and other accessibility tools
- The network scan now supports adding RDP and VNC systems as well in addition to SSH
- You can use multiple KeePassXC databases at the same time
- Add toggle to control whether a service should tunnel a remote port or not
- Add refresh action in connection context menu to easily refresh the system state
- The vault unlock dialog will now provide more feedback on failed unlocks
- Several fixes to be able to run the application in the Android Linux Terminal app without issues
- Improve fallback shell startup checks
Fixes
- Fix flatpak application selections not persisting in the settings
- Fix sftp file system not handling invalid paths properly
- Fix various file browser actions not working properly for symlink entries
- Fix custom icon source directory causing errors when set to a root directory
- Fix local system proxy configuration not being used for license api requests
- Fix host address for cloud systems resetting to unknown in configuration dialog when minimized
- Fix browser navigation bar not showing busy state properly
- Fix other Unix file types like sockets, block devices, and more not being listed in the file browser
- Fix WezTerm not supporting tabs on Windows
- Fix homebrew paths not being set on macOS when using another default shell like fish
- Fix temp file paths to handle xpipe being launched by multiple users
- Fix race condition causing early startup errors sometimes not to be shown
- Fix app not respecting system display scale in KDE
- Fix zellij tab layout on initial terminal launch not being correct
- Fix browser duplicate renames not working for directories
- Fix latest bitwarden update causing XPipe to ask for the master password every time
Downloads
You can find all downloadable artifacts below attached to this release. For installation instructions, see the installation guide.
All artifacts are signed by Christopher Schnick (2E21 05AB FDBA C0EB)