You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/registry/txt.md
+29-11
Original file line number
Diff line number
Diff line change
@@ -26,11 +26,11 @@ wildcard domains will have invalid domain syntax and be rejected by most provide
26
26
27
27
## Encryption
28
28
29
-
Registry TXT records may contain information, such as the internal ingress name or namespace, considered sensitive, , which attackers could exploit to gather information about your infrastructure.
29
+
Registry TXT records may contain information, such as the internal ingress name or namespace, considered sensitive, , which attackers could exploit to gather information about your infrastructure.
30
30
By encrypting TXT records, you can protect this information from unauthorized access.
31
31
32
-
Encryption is enabled by using the `--txt-encrypt-enabled` flag. The 32-byte AES-256-GCM encryption
33
-
key must be specified in URL-safe base64 form, using the `--txt-encrypt-aes-key` flag.
32
+
Encryption is enabled by setting the `--txt-encrypt-enabled`. The 32-byte AES-256-GCM encryption
33
+
key must be specified in URL-safe base64 form (recommended) or be a plain text, using the `--txt-encrypt-aes-key=<key>` flag.
34
34
35
35
Note that the key used for encryption should be a secure key and properly managed to ensure the security of your TXT records.
0 commit comments