Get desktop application:
View/edit binary Protocol Buffers messages
One or more PEM encoded certificates that the client should trust, typically a CA certificate specific to the installation.
The servers that the client should attempt to connect to in <host>:<port> format. E.g. "lazy.com:443", "10.0.0.5:1234"
The client labels that this client should present to the server. Labels indicating the client architecture and OS are automatically included.
If set, the client will use long running persistent connections, otherwise it will make regular short lived polls to the server. Recommended.
If provided, proxy used for connecting to the server. The format is a URL. See https://golang.org/pkg/net/http/#Transport.Proxy for details.
The name of the HTTP header that the client uses to pass its certificate to the server frontend for identification. Required only if the server frontend is configured to use https_header_checksum_config.
If set, used for SNI and certificate validation.
Used in:
Where to persist client state, see NewFilesystemPersistenceHandler for details: https://godoc.org/github.com/google/fleetspeak/fleetspeak/src/client/config#FilesystemPersistenceHandler
Used in:
Where to persist client state, see NewWindowsRegistryPersistenceHandler for details: https://github.com/google/fleetspeak/blob/master/fleetspeak/src/client/config/windows_registry_persistence_handler.go