![]() Install osquery with a persistence service (launchd, systemd, etc.) (default: true) Version for package product (default: 0.0.3)ĭisable TLS certificate verification (default: false) Identifier for package product (default: ) Options: pkg(macOS), msi(Windows), deb(Debian based Linux), rpm(RHEL, CentOS, etc.)Įnroll secret for authenticating to Fleet server The following command-line flags allow you to configure an osquery installer further to communicate with a specific Fleet instance. When the Fleet server uses a self-signed (or otherwise invalid) TLS certificate, package with the -insecure or -fleet-certificate options. deb package configured to communicate with a Fleet server at using the enroll secret notsosecret. The only required parameter is -type, use one of deb, rpm, pkg, or msi.Ĭonfigure osquery to connect to a Fleet (or other TLS) server with the -fleet-url and -enroll-secret flags.Ī minimal invocation for communicating with Fleet: fleetctl package -type deb -fleet-url= -enroll-secret=notsosecret Use fleetctl package to run the packaging tools. msi package generation - Persistence via Services. ![]() rpm (RHEL, CentOS, etc.) package generation - Persistence via systemd. pkg package generation with (optional) notarization and codesigning - Persistence via launchd. ![]() Dependenciesįleetd currently supports building packages on macOS and Linux.īefore building packages, clone or download this repository and install Go.īuilding Windows packages requires Docker to be installed. Tooling is provided with this repository to generate installation packages. Osqueryd - "osqueryremote API (TLS)" -> fleet_server ĭesktop_browser - "My Device API (TLS)" -> fleet_server įleetd is typically deployed via OS-specific packages. Orbit - "Fleet Orbit API (TLS)" -> fleet_server ĭesktop - "Fleet Desktop API (TLS)" -> fleet_server
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |