OutpostX — Next Generation Outpost

OutpostPMX is the next generation of the Outpost Packet Message Manager. The suite initially includes OutpostX and OpTermX and runs on select versions of Windows, Linux, Raspberry Pi OS, and macOS.

Outpost 'Classic' is not going away anytime soon. With so many users on board with Outpost, short of the O/S dropping support for VB6 applications, there are no current plans to sunset Outpost.

The original Outpost development started in 2003 using Microsoft Visual Basic 6. While it served the Amateur Radio community well for over twenty years, the development tools and architecture had reached the point where future enhancements became increasingly difficult.

Conceptually, yes.

Technically, no.

OutpostX is a completely new application, assentially a rewrite of what exists today in Outpost. However, you will see the Outpost operating philosophy in the way OutpostPMX works as soon as you try it. And, with a new set of tools, you will see new features that we always wanted before as well as some differences with how the user interface works. Check out the Quick Start Guide for a preview of these new capabilities.

Absolutely.

Outpost Classic isn't going away. You can continue using it while evaluating OutpostX.

Yes.

Outpost 'Classic' and OutpostX are two separate program with two different message data structures. They can coexist on the same computer.

Not yet.

For the initial beta, the focus is on providing and confirming a solid cross-platform replacement.

The 'X' is my abbreviation for 'cross' as in cross-platform. One of the big project goals for OutpostX was to create a cross-platform solution. This was one of the biggest requests I received over the years. Python and Qt were the answer to this and gave us access to Windows, Linux, and macOS.

• Windows 10
• Windows 11
• Linux x86 64bit, Ubuntu (24.04 and newer)
• Linux arm 64bit, Pi OS (previously called Raspbian)
• macOS Intel x86 64bit

Not every platform has been tested at this point. Support for additional platforms may be added over time. Check the Compatibility page for information about what has been tested, is expected to work, and what is currently unknown.

Currently:

• Serial TNC
• TELNET
• AGWPE API

To date, not every TNC type has been tested. The Kantronics KPC3 has been the primary test bed for development so far. If you have other TNCs that you use, then please give them a try and let me know how it works or if you have problems.

Right now... No. OutpostPMX is freeware. The software license permits redistribution of the complete, unmodified package. This will likely change as the application is built out with more features.

Github is owned by Microsoft (bought back in 2018) and is used by millions of developers and companies like NASA, Google, Microsoft, Python, Qt, and others. With its absorption into Microsoft, the platform has an excellent security reputation.

The bigger risk is really with individual repositories, not GitHub itself.

Personally, I think the real security concerns are (and my mitigation measures):

1. Compromised maintainer account. This is where a developer's GitHub account is hacked. Github enforces mandatory Two-Factor Authentication for all active contributors, thereby significantly reducing generic account takeovers across the platform.
2. Downloading unofficial forks. This is where someone can create a copy (fork) of a repository and offer it as an Outpost ‘Enhanced’ version. My recommendation is: (i) Always download from the Outpost official website (links to github for the installer ONLY), and (ii) verify the repository owner in the download url (for me, it is github.com/Jimo706/outpostpmx/...).
3. Unsigned binaries. Today, I digitally sign all windows programs associated with a release. This was needed from my experience wiht Outpost and aggressive virus programs that were starting to quarantine or delete Outpost programs.
   My plan is to sign up as a macOS developer to get the macOS release signed and Apple-notorized.