mirror of
https://github.com/outbackdingo/firezone.git
synced 2026-01-27 10:18:54 +00:00
bed94a1d21
This PR adds the equivalent MDM configuration that we already have for MacOS & iOS for the GUI client on Windows. These options are retrieved from the Windows registry when the Client is started. Specifically, the key for these is: `HKEY_CURRENT_USER\Software\Policies\Firezone`. At moment, these cannot be configured or seen by the user. They are also not "watched" for whilst the Client is running. If an admin pushes a new MDM configuration, the Client will have to be restarted in order for that new config to take effect. Windows Policy templates are structured into two files: - An `.admx` file that defines the structure of the policy, like the kinds of values it has, where it is stored, which versions it is supported on and which category it belongs to. - An `.adml` file that defines defines all strings and presentation logic, like the actual text of the policies and how the values are presented in the GUI in e.g. Intune. Internally, we differentiate between `MdmSettings` and `AdvancedSettings`. The `MdmSettings` are cross-platform, however on Linux, we always fallback to the defaults and therefore, they are always "unset". Eventually, it might make sense to wrap both of these into a more general `Settings` struct that acts as as a proxy for the two. Related: #4505
21 lines
491 B
TOML
21 lines
491 B
TOML
[package]
|
|
name = "admx-macro"
|
|
version = "0.1.0"
|
|
edition = { workspace = true }
|
|
description = "Proc macro to generate Windows registry loading code from ADMX policy templates"
|
|
license = { workspace = true }
|
|
|
|
[lib]
|
|
path = "lib.rs"
|
|
proc-macro = true
|
|
test = false # Somehow buggy, tests don't compile on CI?
|
|
|
|
[dependencies]
|
|
proc-macro2 = { workspace = true }
|
|
quote = { workspace = true }
|
|
roxmltree = { workspace = true }
|
|
syn = { workspace = true, features = ["full"] }
|
|
|
|
[lints]
|
|
workspace = true
|