AWS privateca documentation change
Summary
Updated AWS CLI file prefix guidance from version-specific instructions to general examples using 'fileb://' with backward compatibility note for older CLI versions
Security assessment
This change clarifies file prefix usage for Base64-encoded data parsing but doesn't address any security vulnerability or weakness. It's a documentation improvement for correct command syntax.
Diff
diff --git a/privateca/latest/userguide/PCACertInstall.md b/privateca/latest/userguide/PCACertInstall.md index fe5d50d75..d7de38088 100644 --- a//privateca/latest/userguide/PCACertInstall.md +++ b//privateca/latest/userguide/PCACertInstall.md @@ -200 +200 @@ This yields output similar to the following. -If you are using AWS CLI version 1.6.3 or later, use the prefix `fileb://` when specifying the required input file. This ensures that AWS Private CA parses the Base64-encoded data correctly. +The examples below use the prefix `fileb://` to load required input files, ensuring that AWS Private CA parses Base64-encoded data correctly. If you are using AWS CLI version older than 1.6.3, use `file://` instead. @@ -204 +204 @@ If you are using AWS CLI version 1.6.3 or later, use the prefix `fileb://` when - --csr file://ca.csr \ + --csr fileb://ca.csr \ @@ -309 +309 @@ This yields output similar to the following. -If you are using AWS CLI version 1.6.3 or later, use the prefix `fileb://` when specifying the required input file. This ensures that AWS Private CA parses the Base64-encoded data correctly. +The examples below use the prefix `fileb://` to load required input files, ensuring that AWS Private CA parses Base64-encoded data correctly. If you are using AWS CLI version older than 1.6.3, use `file://` instead. @@ -313 +313 @@ If you are using AWS CLI version 1.6.3 or later, use the prefix `fileb://` when - --certificate file://cert.pem + --certificate fileb://cert.pem