Explore our security philosophy, understand protection limits, access threat intelligence, and support the project.
Connect with the BastionGuard community, report bugs, and access tools to identify potential phishing threats.
Explore BastionGuard's documentation, screenshots, developer resources, and open-source code.
Download BastionGuard's endpoint security solutions for Linux desktops and Android devices.
Access security advisories, vulnerability reporting guidelines, CVE records, and responsible disclosure information.
Discover the people, principles, and vision behind BastionGuard, and learn how to support the project's development.
RootGuard ships native definitions for systemd, OpenRC, dinit and SysV init. Select one explicitly for distribution packaging:
Accepted values are:
The compatibility aliases sysv and dninit are normalized to sysvinit and dinit. The canonical spelling is dinit.
For local builds, auto checks PID 1 first and then runtime markers. It does not select systemd merely because a compatibility systemctl binary exists. OpenRC and SysV definitions are never installed together because both own /etc/init.d/bastionguard-rootguard.
All init definitions are also installed as samples below /usr/share/bastionguard-rootguard/init-samples/.
The GTK client calls the multi-init controller:
Read-only status is unprivileged. Start, stop, restart and policy reload are executed through pkexec and the bundled polkit action.
BastionGuard is designed for system protection, real-time monitoring, and defense against threats such as ransomware and persistent attacks.
© 2025–2026 BastionGuard™. All Rights Reserved. BastionGuard™ was filed by Calogero Scarnà with the Italian Patent and Trademark Office (UIBM) on 16/12/2025 – Application No. 302025000196519. The BastionGuard™ name and branding are not licensed under the GPLv3. Source code released under the GNU General Public License v3 (GPLv3). ClamAV® is a registered trademark of Cisco.