We are pleased to announce that the official BastionGuard Linux repositories have been successfully built, cryptographically signed, verified, and published.
BastionGuard packages are now available for the following supported Linux distributions:
- Debian 13 “Trixie”
- Ubuntu 25.10
- Ubuntu 26.04
- Fedora 44
- Mageia 10
- OpenMandriva Lx 6.0 Rock
- openSUSE Tumbleweed
- openSUSE Leap 16.0
Each repository provides packages signed with the official BastionGuard signing key.
Users can now install and update BastionGuard directly through the native package manager of their Linux distribution.
Repository Availability
All distribution-specific repositories have completed the publication process.
Each repository has been:
- Built
- Cryptographically signed
- Indexed
- Verified
- Published
Repository metadata, package indexes, signing information, and installation instructions are now available through the official BastionGuard website.
Installing BastionGuard
The repository installation guide provides the commands required to:
- add the official BastionGuard repository;
- install the repository signing key;
- refresh package metadata;
- install BastionGuard;
- receive future updates through the system package manager.
Installation instructions are available at:
Install BastionGuard from the official Linux repositories
Init-System Support in BastionGuard 2.0
Starting with BastionGuard 2.0, the following init systems are officially supported:
- systemd
- OpenRC
- SysVinit
- Dinit
This broader init-system support improves compatibility across Linux distributions and different system configurations.
BastionGuard keeps init-system detection and service-management logic outside the main C++ application code wherever possible.
Common Service Dispatcher
The application-facing service command is:
/usr/libexec/bastionguard/bastionguard-service
The same dispatcher can manage both system-level and user-level BastionGuard services.
System-Service Examples
bastionguard-service --system enable --now bsc-daemon.service
bastionguard-service --system status bsc-daemon.service
bastionguard-service --system logs bsc-daemon.service 100
User-Service Examples
bastionguard-service --user enable --now BastionGuard-pacd.service
bastionguard-service --user status BastionGuard-pacd.service
The dispatcher automatically translates these operations to the appropriate service-management commands for the active init system:
systemctlfor systemd;rc-serviceandrc-updatefor OpenRC;- the corresponding service-management tools for SysVinit;
dinitctlfor Dinit.
This provides a consistent BastionGuard service-management interface regardless of the init system used by the distribution.
Reload Behavior
The bsc-daemon service does not expose a dedicated reload procedure.
An explicit reload request returns exit code 3, indicating that the operation is not supported.
The try-reload-or-restart operation performs a restart when a dedicated reload procedure is unavailable.
Package Verification
Users should install BastionGuard only from the official repositories or official installation packages published by the BastionGuard project.
The repository signing key allows the package manager to verify the authenticity and integrity of downloaded packages and repository metadata.
Updates
Once the official repository has been configured, future BastionGuard releases and package updates can be installed through the distribution’s normal update process.
Debian and Ubuntu
sudo apt update
sudo apt upgrade
Fedora
sudo dnf upgrade
openSUSE
sudo zypper refresh
sudo zypper update
Mageia and OpenMandriva
sudo urpmi.update -a
sudo urpmi --auto-select
The exact commands may vary depending on the Linux distribution and package manager configuration.
Official Links
- Official BastionGuard repository portal
- Repository installation guide
- BastionGuard documentation
- Report bugs and feature requests
Thank you for your patience and continued support of the BastionGuard project.



