jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-18 23:06:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

Content Trust more-info (#17061)

Browse Source 
* Content Trust more-info

* base untrusted

* Update untrusted.markdown

* Update source/more-info/unhealthy/untrusted.markdown

Co-authored-by: Philip Allgaier <mail@spacegaier.de>

* Update source/more-info/unsupported/content_trust.markdown

Co-authored-by: Philip Allgaier <mail@spacegaier.de>

* Update source/more-info/unsupported/content_trust.markdown

Co-authored-by: Philip Allgaier <mail@spacegaier.de>

Co-authored-by: Philip Allgaier <mail@spacegaier.de>
This commit is contained in:
Pascal Vizeli 2021-03-30 11:45:13 +02:00 committed by GitHub
parent 29ac6acf32
commit 78cdc5da2e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 37 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
source/more-info/unhealthy/untrusted.markdown Normal file
View File

@ -0,0 +1,12 @@
---
title: "System detected untrusted content"
description: "More information on why untrusted content marks an installation as unhealthy."
---
## The issue
Home Assistant detected untrusted code. It looks like someone/something tried to inject not signed images or code into your Home Assistant system. But don't worry, we blocked this action and nothing was applied.
## The solution
Please make sure your network is not affected by an intruder and try it again. To reset this status, you need to restart the Supervisor.

25
source/more-info/unsupported/content_trust.markdown Normal file
View File

@ -0,0 +1,25 @@
---
title: "Ignored content trust"
description: "More information on why disabling content-trust marks the installation as unsupported."
---
## The issue
You have disabled the content-trust check. That means Home Assistant can't verify anymore if the content is trusted and was not modified by attackers.
We strongly recommend to have this check enabled.
For content-trust, we use the open source solution [CodeNotary](https://codenotary.io).
## The solution
To resolve this status, you need to re-enable the content-trust protection mechanism by using the CLI:
```bash
ha supervisor options --content-trust
```
When you have enabled the content-trust, restart the Supervisor.
```bash
ha supervisor restart
```