Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: update disk-encryption.md #10194

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

greenpsi
Copy link

Pull Request

What? (description)

Add note about required DHCP server when using kms disk encryption

Why? (reasoning)

Acceptance

Please use the following checklist:

  • you linked an issue (if applicable)
  • you included tests (if applicable)
  • you ran conformance (make conformance)
  • you formatted your code (make fmt)
  • you linted your code (make lint)
  • you generated documentation (make docs)
  • you ran unit-tests (make unit-tests)

See make help for a description of the available targets.

Add note about required DHCP server when using kms disk encryption

Signed-off-by: greenpsi <[email protected]>
@DmitriyMV
Copy link
Member

Greetings! Thanks for the PR. Can you also update 1.10 docs?

@@ -37,6 +37,9 @@ Talos Linux supports four encryption methods, which can be combined together for
> Note: `nodeID` encryption is not designed to protect against attacks where physical access to the machine, including the drive, is available.
> It uses the hardware characteristics of the machine in order to decrypt the data, so drives that have been removed, or recycled from a cloud environment or attached to a different virtual machine, will maintain their protection and encryption.
> Note: When using kms encryption, a DHCP server is required for the talos nodes, as the static Network configuration is only loaded after the disk is decrypted.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure this is entirely correct based on how static network info is provided, if it's kernel cmdline I think it should work, am I right @smira ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, and it also depends on STATE/EPHEMERAL, and network config might come from too many place. but if you have your static network config in STATE, of course using KMS doesn't make sense

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants