use consistent term for key provisioning
This commit is contained in:
parent
dd155a987d
commit
cdc6704924
@ -659,7 +659,7 @@
|
|||||||
|
|
||||||
<ul>
|
<ul>
|
||||||
<li>Sandboxed Google Play compatibility layer: substantially improve dynamite module support</li>
|
<li>Sandboxed Google Play compatibility layer: substantially improve dynamite module support</li>
|
||||||
<li>use GrapheneOS hardware attestation certificate provisioning server by default with a toggle added to Settings to choose the server similar to connectivity checks</li>
|
<li>use GrapheneOS hardware attestation key provisioning server by default with a toggle added to Settings to choose the server similar to connectivity checks</li>
|
||||||
<li>extend eSIM management code with disabling the apps in secondary users due to prior GrapheneOS releases enabling them in all users</li>
|
<li>extend eSIM management code with disabling the apps in secondary users due to prior GrapheneOS releases enabling them in all users</li>
|
||||||
<li>move early boot eSIM integration code later in an attempt to fix a potential regression</li>
|
<li>move early boot eSIM integration code later in an attempt to fix a potential regression</li>
|
||||||
<li>Vanadium: update Chromium base to 100.0.4896.58</li>
|
<li>Vanadium: update Chromium base to 100.0.4896.58</li>
|
||||||
|
Loading…
x
Reference in New Issue
Block a user