66 lines
2.0 KiB
Plaintext
66 lines
2.0 KiB
Plaintext
Source: vesperprofiled
|
|
Section: admin
|
|
Priority: optional
|
|
Maintainer: oxmc <packages@oxmc.me>
|
|
Build-Depends:
|
|
debhelper-compat (= 13),
|
|
cmake (>= 3.18),
|
|
libssl-dev (>= 3.0),
|
|
libyaml-dev,
|
|
libdbus-1-dev,
|
|
libsystemd-dev,
|
|
libcurl4-openssl-dev,
|
|
pkg-config
|
|
Standards-Version: 4.7.0
|
|
Homepage: https://vesperos.oxmc.me
|
|
Vcs-Git: https://git.oxmc.me/vesperos/vesperprofiled.git
|
|
|
|
Package: vesperprofiled
|
|
Architecture: any
|
|
Depends:
|
|
${shlibs:Depends},
|
|
${misc:Depends},
|
|
vesperprofiled-config-schema (>= 1.0.0),
|
|
libssl3 (>= 3.0),
|
|
libyaml-0-2,
|
|
libdbus-1-3,
|
|
libsystemd0,
|
|
libcurl4,
|
|
dbus,
|
|
network-manager,
|
|
ca-certificates
|
|
Recommends:
|
|
cloud-init,
|
|
nftables,
|
|
network-manager-strongswan,
|
|
network-manager-l2tp,
|
|
libnss3-tools,
|
|
libpam-pwquality,
|
|
libpam-faillock,
|
|
unattended-upgrades,
|
|
dconf-cli,
|
|
tpm2-tools
|
|
Suggests:
|
|
vesper-zte-server,
|
|
vesperos-ca
|
|
Description: VesperOS configuration profile daemon with Zero-Touch Enrollment
|
|
vesperprofiled is the unified device management daemon for VesperOS.
|
|
It ships as a single binary containing two subsystems:
|
|
.
|
|
Profile Service — parses, verifies, and applies .vconfig configuration
|
|
profiles. Profiles are YAML files optionally wrapped in a CMS/PKCS#7
|
|
signed envelope. Which payload types are accepted is controlled by the
|
|
installed vesperprofiled-config-schema package, allowing OEMs to restrict
|
|
the available configuration surface for their platform.
|
|
.
|
|
ZTE Client — Zero-Touch Enrollment. Collects hardware identity (DMI UUID,
|
|
system/board serial, machine-id, permanent MAC addresses, EFI GUID) and
|
|
queries a ZTE lookup server on first internet connection. If the device is
|
|
registered, the signed MDM enrollment profile is downloaded and installed
|
|
automatically. Deferred enrollment is fully supported: if no network is
|
|
available at first boot, the ZTE client enrolls on first connectivity.
|
|
.
|
|
The profile service is exposed as a D-Bus system service at
|
|
me.oxmc.vesperos.ProfileService. The ZTE client runs as a background
|
|
thread in the same process.
|