[neon/ubuntu-core] /: Stresses what signature happens for dangerous images too

[Kevin Ottens]

Git commit 62a30e4f9fd6e51146534c95a4f108ffcca1d013 by Kevin Ottens.
Committed on 02/04/2024 at 09:05.
Pushed by ervin into branch 'master'.

Stresses what signature happens for dangerous images too

M  +2    -0    README.md

https://invent.kde.org/neon/ubuntu-core/-/commit/62a30e4f9fd6e51146534c95a4f108ffcca1d013

diff --git a/README.md b/README.md
index 28559c9..ae5a951 100644
--- a/README.md
+++ b/README.md
@@ -22,6 +22,8 @@ Also, no build can occur if you're not authenticated in your Ubuntu One account
 
 ### dangerous vs signed
 
+Whatever image variant you build, despite what the name seems to imply, some signature will occur. So they both require a valid key as described in the previous section.
+
 The main difference between the dangerous and the signed images is the amount of freedom you get as to their content. The signed image will contain only the snaps listed in `kde-neon-core-amd64.json`. The dangerous image allows you to inject extra snaps or override some of the snaps of the list with locally built one.
 
 As a developer, `make dangerous` is probably what you will want to use most of the time. To inject or override snaps, simply drop your own snaps in the `local-snaps` directory. Any snap in this directory will be injected in the dangerous image.