Your entire server infrastructure at your fingertips
APACHE-2.0 License
Bot releases are visible (Hide)
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "10.2.1"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 10.2.1
Automated VirusTotal analysis of all artifacts:
All artifacts are signed with the following gpg key: https://xpipe.io/signatures/crschnick.gpg
Published by crschnick 3 months ago
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "10.2"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 10.2
Automated VirusTotal analysis of all artifacts:
All artifacts are signed with the following gpg key: https://xpipe.io/signatures/crschnick.gpg
Published by crschnick 3 months ago
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "10.1.1"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 10.1.1
Automated VirusTotal analysis of all artifacts:
All artifacts are signed with the following gpg key: https://xpipe.io/signatures/crschnick.gpg
Published by crschnick 3 months ago
Feedback showed that the file browser transfer pane in the bottom left was confusing and unintuitive to use. Therefore, it has now been changed to be a more straightforward download area. You can drag files into it to automatically download them. From there you can either drag them directly where you want them to be in your local desktop environment or move them into the downloads directory.
There is now the possibility to jump to a file in a directory by typing the first few characters of its name.
There were also a couple of bug fixes:
Several new endpoints have been added to widen the capabilities for external clients:
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "10.1"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 10.1
Automated VirusTotal analysis of all artifacts:
All artifacts are signed with the following gpg key: https://xpipe.io/signatures/crschnick.gpg
Published by crschnick 4 months ago
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "10.0.4"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 10.0.4
Automated VirusTotal analysis of all artifacts:
All artifacts are signed with the following gpg key: https://xpipe.io/signatures/crschnick.gpg
Published by crschnick 4 months ago
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "10.0.3"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 10.0.3
Automated VirusTotal analysis of all artifacts:
All artifacts are signed with the following gpg key: https://xpipe.io/signatures/crschnick.gpg
Published by crschnick 4 months ago
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "10.0.2"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 10.0.2
Automated VirusTotal analysis of all artifacts:
All artifacts are signed with the following gpg key: https://xpipe.io/signatures/crschnick.gpg
Published by crschnick 4 months ago
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "10.0.1"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 10.0.1
Automated VirusTotal analysis of all artifacts:
All artifacts are signed with the following gpg key: https://xpipe.io/signatures/crschnick.gpg
Published by crschnick 4 months ago
There is now a new HTTP API for the XPipe daemon, which allows you to programmatically manage remote systems. You can find details and an OpenAPI specification at the new API button in the sidebar. The API page contains everything you need to get started, including code samples for various different programming languages.
To start off, you can query connections based on various filters. With the matched connections, you can start remote shell sessions for each one and run arbitrary commands in them. You get the command exit code and output as a response, allowing you to adapt your control flow based on command outputs. Any kind of passwords and other secrets are automatically provided by XPipe when establishing a shell connection. You can also access the file systems via these shell connections to read and write remote files.
There already exists a community made XPipe API library for python and a python CLI client. These tools allow you to interact with the API more ergonomically and can also serve as an inspiration of what you can do with the new API. If you also built a tool to interact with the XPipe API, you can let me know and I can compile a list of community development projects.
Many systems run a variety of different services such as web services and others. There is now support to detect, forward, and open the services. For example, if you are running a web service on a remote container, you can automatically forward the service port via SSH tunnels, allowing you to access these services from your local machine, e.g. in a web browser. These service tunnels can be toggled at any time. The port forwarding supports specifying a custom local target port and also works for connections with multiple intermediate systems through chained tunnels. For containers, services are automatically detected via their exposed mapped ports. For other systems, you can manually add services via their port.
You can use an unlimited amount of local services and one active tunneled service in the community edition.
The scripting system has been reworked. There have been several issues with it being clunky and not fun to use. The new system allows you to assign each script one of multiple execution types. Based on these execution types, you can make scripts active or inactive with a toggle. If they are active, the scripts will apply in the selected use cases. There currently are these types:
myscript.sh
, also with arguments.If you have existing scripts, they will have to be manually adjusted by setting their execution types.
The docker integration has been updated to support docker contexts. You can use the default context in the community edition, essentially being the same as before as XPipe previously only used the default context. Support for using multiple contexts is included in the professional edition.
There's now support for Windows docker containers running on HyperV.
Note that old docker container connections will be removed as they are incompatible with the new version.
You can now automatically open the Proxmox dashboard website through the new service integration. This will also work with the service tunneling feature for remote servers.
You can now open VNC sessions to Proxmox VMs.
The Proxmox professional license requirement has been reworked to support one non-enterprise PVE node in the community edition.
The toggle to show only running connections will now no longer actually remove the connections internally and instead just not display them. This will reduce git vault updates and is faster in general.
You can now order connections relative to other sibling connections. This ordering will also persist when changing the global order in the top left.
The UI has also been streamlined to make common actions and toggles more easily accessible.
xpipe open -d "<dir>"
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "10.0"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 10.0
Published by crschnick 4 months ago
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "9.4.1"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 9.4.1
Automated VirusTotal analysis of all artifacts:
All artifacts are signed with the following gpg key: https://xpipe.io/signatures/crschnick.gpg
Published by crschnick 5 months ago
There is now the new option to add notes to any connection. These notes are written in markdown, and the full markdown spec is supported.
The file transfer mechanism when editing files had some flaws, which under rare conditions caused the data not being fully transferred or the file browser session to timeout/die. This was especially prevalent when saving a file multiple times in quick succession or when using VSCode on Windows, which performs multiple file writes on save (for whatever reason).
The entire transfer implementation has been rewritten to iron out these issues and increase reliability. Other file browser actions have also been made more reliable.
There seems to be another separate issue with a PowerShell bug when connecting to a Windows system, causing file uploads to be slow. For now, xpipe can fall back to pwsh if it is installed to work around this issue.
The conflict resolution has been improved
The terminal integration got reworked for some terminals:
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "9.4"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 9.4
Automated VirusTotal analysis of all artifacts:
All artifacts are signed with the following gpg key: https://xpipe.io/signatures/crschnick.gpg
Published by crschnick 5 months ago
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "9.3"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 9.3
Automated VirusTotal analysis of all artifacts:
All artifacts are signed with the following gpg key: https://xpipe.io/signatures/crschnick.gpg
Published by crschnick 5 months ago
The file browser has been reworked to support many new keyboard shortcuts, plus the general user experience has been improved:
The git error actions have been reworked. In case any merge conflict or similar occurs, the possible actions are now handled better:
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "9.2"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 9.2
Automated VirusTotal analysis of all artifacts:
All artifacts are signed with the following gpg key: https://xpipe.io/signatures/crschnick.gpg
Published by crschnick 6 months ago
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "9.1"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 9.1
Automated VirusTotal analysis of all artifacts:
All artifacts are signed with the following gpg key: https://xpipe.io/signatures/crschnick.gpg
Published by crschnick 6 months ago
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.
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
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.
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 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.
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.
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.
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.
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.
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.
There have been countless small bug fixes across the board. They are not listed individually here, but hopefully you will notice some of them.
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "9.0.1"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 9.0.1
Automated VirusTotal analysis of all artifacts:
All artifacts are signed with the following gpg key: https://xpipe.io/signatures/crschnick.gpg
Published by crschnick 6 months ago
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.
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
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.
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 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.
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.
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.
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.
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.
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.
There have been countless small bug fixes across the board. They are not listed individually here, but hopefully you will notice some of them.
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "9.0"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 9.0
Automated VirusTotal analysis of all artifacts:
All artifacts are signed with the following gpg key: https://xpipe.io/signatures/crschnick.gpg
Published by crschnick 7 months ago
There is now the possibility to use XPipe professional for free for students and faculty from accredited educational institutions (high schools, colleges, and universities). Just send an email to [email protected] with your official email address of your educational institution.
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "8.6"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 8.6
Automated VirusTotal analysis of all artifacts:
Published by crschnick 7 months ago
There was some feedback that the available plans for the professional edition were confusing. The monthly subscription and one time purchase could easily be confused as basically the same thing with a different timespan. Even the FAQ could still not eliminate all points of confusion as most readers were already familiar with plans from other tools, so it was difficult to properly break up the terms.
While the monthly subscription did serve well as a cheap trial of some sorts, the community edition does almost the same job as most functionality is also available in there for noncommercial systems. Most people were also wary of subscriptions and interpreted the one-time purchase option as just a longer subscription even though that is not the case. There were also several other problems such as payment limitations with the subscription and no easy way to convert an existing subscription into the one-time purchase.
With this update, the monthly subscription will be retired. This makes it much easier to explain what you will get when purchasing the professional edition without having to differentiate between two completely different models. If you are currently using the monthly subscription, nothing will change for you. It will just not be possible for new customers to purchase it anymore.
The website at https://xpipe.io has also been updated with the updated professional edition structure and will now hopefully explain everything better.
There's also now a lifetime professional edition available, which will include all future pro features. You can find the details for that on the pricing page in the FAQ if you are interested.
sh
shells with Bad substitution
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "8.5"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 8.5
Automated VirusTotal analysis of all artifacts:
Published by crschnick 7 months ago
This update will restore the old behavior of sudo passwords being automatically sourced from connection details when possible, e.g. an SSH login password or a set WSL password.
This behavior can also be combined with the option to always confirm elevation access in the security settings if you don't want XPipe to automatically fill in your sudo password.
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "8.4"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 8.4
Automated VirusTotal analysis of all artifacts:
Published by crschnick 7 months ago
xpipe-io.xpipe
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "8.3"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 8.3
Automated VirusTotal analysis of all artifacts: