92 lines
1.8 KiB
Text
92 lines
1.8 KiB
Text
Source: bastionguard
|
|
Section: utils
|
|
Priority: optional
|
|
Maintainer: Caogero Scarnà <info@bastionguard.eu>
|
|
Build-Depends:
|
|
debhelper-compat (= 13),
|
|
build-essential,
|
|
cmake,
|
|
pkg-config,
|
|
gettext,
|
|
libgtkmm-4.0-dev,
|
|
libsigc++-3.0-dev,
|
|
libsoup-3.0-dev,
|
|
libsecret-1-dev,
|
|
libudev-dev,
|
|
libidn2-dev,
|
|
libsqlite3-dev,
|
|
libcurl4-openssl-dev,
|
|
libssl-dev,
|
|
libboost-thread-dev,
|
|
libre2-dev,
|
|
libhyperscan-dev,
|
|
nlohmann-json3-dev,
|
|
libyara-dev,
|
|
libpolkit-gobject-1-dev,
|
|
libsmbclient-dev,
|
|
libsystemd-dev,
|
|
rsync,
|
|
meson,
|
|
ninja-build,
|
|
python3,
|
|
git,
|
|
libffi-dev,
|
|
zlib1g-dev,
|
|
libmount-dev,
|
|
libpcre2-dev,
|
|
libpng-dev,
|
|
libjpeg-dev,
|
|
libtiff-dev,
|
|
libwebp-dev,
|
|
libfribidi-dev,
|
|
libx11-dev,
|
|
libxcursor-dev,
|
|
libxrandr-dev,
|
|
libxi-dev,
|
|
libxinerama-dev,
|
|
libxdamage-dev,
|
|
libxcomposite-dev,
|
|
libxfixes-dev,
|
|
libxkbcommon-dev,
|
|
libwayland-dev,
|
|
wayland-protocols,
|
|
libasound2-dev,
|
|
libglibmm-2.4-dev,
|
|
libglibmm-2.68-dev,
|
|
gperf,
|
|
libxml2-dev,
|
|
libgstreamer1.0-dev,
|
|
libgstreamer-plugins-base1.0-dev,
|
|
libgstreamer-plugins-bad1.0-dev
|
|
Standards-Version: 4.6.2
|
|
Rules-Requires-Root: no
|
|
Homepage: https://bastionguard.eu
|
|
|
|
|
|
Package: bastionguard
|
|
Architecture: amd64
|
|
Depends:
|
|
${shlibs:Depends},
|
|
${misc:Depends},
|
|
clamav,
|
|
clamav-daemon,
|
|
clamav-freshclam,
|
|
nginx,
|
|
php-fpm,
|
|
polkitd,
|
|
dnsmasq,
|
|
rsync,
|
|
curl,
|
|
yara
|
|
Description: Transparent security control plane for Linux desktops
|
|
BastionGuard is not a "trust us" security product.
|
|
It is a security control plane for Linux desktops where every protection
|
|
mechanism is explicit, deterministic, and observable.
|
|
.
|
|
Unlike most desktop security tools, which hide decisions behind opaque
|
|
engines, cloud scoring, or silent automation, BastionGuard exposes
|
|
what is happening, why it is happening, and how protections are applied.
|
|
Users and administrators can see, control, and reason about every
|
|
security decision.
|
|
|
|
|