GrapheneOS on Nostr: Our auto-reboot implementation builds upon our other hardening which protects the ...
Our auto-reboot implementation builds upon our other hardening which protects the device. We use default enabled hardware-level + software-level disabling of USB-C data while locked, default enabled aggressive use of hardware memory tagging in a hardened allocator and a lot more.
Published at
2024-11-09 00:41:53Event JSON
{
"id": "6162d795398bb763290e85567a37c2bba60a65fd98adee4b3adfe0f95dfa6c65",
"pubkey": "5468bceeb74ce35cb4173dcc9974bddac9e894a74bf3d44f9ca8b7554605c9ed",
"created_at": 1731112913,
"kind": 1,
"tags": [
[
"e",
"0d34fefccff5a555003e3cc43e52c851b374b300d38dc92bc1b4869c86362d9e",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://grapheneos.social/users/GrapheneOS/statuses/113450215897626825",
"activitypub"
]
],
"content": "Our auto-reboot implementation builds upon our other hardening which protects the device. We use default enabled hardware-level + software-level disabling of USB-C data while locked, default enabled aggressive use of hardware memory tagging in a hardened allocator and a lot more.",
"sig": "2714f168ec536e632463a6d3b3caa934767c01e38d7221ec3004bacc53adc1bd32b2395c37937ec5d94b551c1e143897f3bac7ab053d6192f54151eb01a39546"
}
