fix(aes-encryption): rephrase encryption message

Signed-off-by: ivan katliarchuk <ivan.katliarchuk@gmail.com>
This commit is contained in:
ivan katliarchuk 2024-12-29 15:10:58 +00:00
parent b711ceb4bf
commit fe3d4c1344
No known key found for this signature in database
GPG Key ID: 601CDBBBB76E47BE

View File

@ -29,8 +29,8 @@ wildcard domains will have invalid domain syntax and be rejected by most provide
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.
By encrypting TXT records, you can protect this information from unauthorized access.
Encryption is enabled by using the `--txt-encrypt-enabled` flag. The 32-byte AES-256-GCM encryption
key must be specified in URL-safe base64 form, using the `--txt-encrypt-aes-key` flag.
Encryption is enabled by setting the `--txt-encrypt-enabled` flag to `true`. The 32-byte AES-256-GCM encryption
key must be specified in URL-safe base64 form (recommended) or be a plain text, using the `--txt-encrypt-aes-key` flag.
Note that the key used for encryption should be a secure key and properly managed to ensure the security of your TXT records.