Is my chromebook still safe ?

[Gianluca Cavallo]

hello,

After I found this error on my chromebook:

 trusted_key: device-mapper: crypt: dm-6: INTEGRITY AEAD ERROR, sector 2097024

I performed a powerwash.

Now I found this error:

[  1.805683] WARNING chromeos_startup: [security_manager.cc(191)] Missing trusted DLC verity digests file.: No such file or directory (2) [  1.805711] WARNING chromeos_startup: [security_manager.cc(204)] Forcing LoadPin to ingest /dev/null. [  1.805724] WARNING chromeos_startup: [security_manager.cc(211)] Unable to setup trusted DLC verity digests: Invalid argument (22) [  1.805738] WARNING chromeos_startup: [chromeos_startup.cc(372)] Failed to setup LoadPin verity digests. [  1.808651] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.

So my question is:

Is my chromebook stll safe ?

Are my data are still encrypted and the integrity of my device protected ?

If it is not, how can I restore the device data integrity and encryption without to enable the developer mode ?

I underline that I NEVER enable the developer mode. I don't want to lost the upgrade and the effective of the titan chip... if it is still valid.

Thanks for all the tips and suggestions.

[Jae Hoon Kim]

On Tue, Jul 2, 2024 at 10:27 PM Gianluca Cavallo <cavallo.gianl...@gmail.com> wrote:

hello,

After I found this error on my chromebook:

 trusted_key: device-mapper: crypt: dm-6: INTEGRITY AEAD ERROR, sector 2097024

I performed a powerwash.

Now I found this error:

[  1.805683] WARNING chromeos_startup: [security_manager.cc(191)] Missing trusted DLC verity digests file.: No such file or directory (2) [  1.805711] WARNING chromeos_startup: [security_manager.cc(204)] Forcing LoadPin to ingest /dev/null. [  1.805724] WARNING chromeos_startup: [security_manager.cc(211)] Unable to setup trusted DLC verity digests: Invalid argument (22) [  1.805738] WARNING chromeos_startup: [chromeos_startup.cc(372)] Failed to setup LoadPin verity digests. [  1.808651] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.

So my question is:

Is my chromebook stll safe ?

Most likely Gianluca, however, I can't say without looking at your device logs.

The initial portion of your logs seem to suggest that there was some sort of corruption (maybe filesystem).

Nonetheless, the newer logs are merely warnings, and thus can be disregarded.

 

Are my data are still encrypted and the integrity of my device protected ?

If it is not, how can I restore the device data integrity and encryption without to enable the developer mode ?

I underline that I NEVER enable the developer mode. I don't want to lost the upgrade and the effective of the titan chip... if it is still valid.

Assuming that you have not tampered with developer mode, you can submit a listnr report for someone to investigate.

Please file a bug by following these steps: https://www.chromium.org/chromium-os/developer-library/guides/bugs/reporting-bugs/

 

Thanks for all the tips and suggestions.

--
--
ChromiumOS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-dev
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-d...@chromium.org.

--

-Jae