After the initial verification, which results in pairing, performing verification - against between the same Auditor and Auditee (as long as the app data hasn't been + again between the same Auditor and Auditee (as long as the app data hasn't been cleared) will provide strong validation of the identity and integrity of the device. That makes it best to get the pairing done right after installation. You can also consider setting up the optional remote attestation service.
diff --git a/static/usage.html b/static/usage.html index e0193de3..622812d1 100644 --- a/static/usage.html +++ b/static/usage.html @@ -743,7 +743,7 @@In the stock OS, the default is to use a unique persistent random MAC address for each network. It has 2 options available: "Use randomized MAC (default)" and "Use device MAC". In GrapheneOS, the default is generating a new random MAC address when - connecting to a network. It has 3 options available: "Use fully randomized MAC + connecting to a network. It has 3 options available: "Use per-connection randomized MAC (default)", "Use per-network randomized MAC" and "Use device MAC".
The DHCP client uses the anonymity profile rather than sending a hostname