303-300 · Question #2
Which of the following lines in an OpenSSL configuration adds an X 509v3 Subject Alternative
The correct answer is A. subjectAltName = DNS: www.example.org, DNS:example.org. Option A uses the correct OpenSSL configuration syntax for adding an X.509v3 Subject Alternative Name (SAN) extension: the directive subjectAltName followed by = and comma-separated DNS: prefixed values, which is exactly how OpenSSL's [req_ext] or [v3_req] section expects SAN…
Question
Which of the following lines in an OpenSSL configuration adds an X 509v3 Subject Alternative
Options
- AsubjectAltName = DNS: www.example.org, DNS:example.org
- Bextension=SAN: www.example.org, SAN:example.org
- CsubjectAltName: www.example.org, subjectAltName: example.org
- DcommonName = subjectAltName= www.example.org, subjectAltName = example.org
- Esubjects: CN= www.example.org, CN=example.org
How the community answered
(55 responses)- A76% (42)
- B5% (3)
- C2% (1)
- D15% (8)
- E2% (1)
Explanation
Option A uses the correct OpenSSL configuration syntax for adding an X.509v3 Subject Alternative Name (SAN) extension: the directive subjectAltName followed by = and comma-separated DNS: prefixed values, which is exactly how OpenSSL's [req_ext] or [v3_req] section expects SAN entries to be written.
Why the distractors fail:
- B uses
extension=SAN:which is not valid OpenSSL syntax - SANs are not declared with a genericextension=key - C uses colons (
:) instead of equals signs (=) for the directive assignment, and repeats the key name rather than comma-separating values on one line - D incorrectly places SAN values inside the
commonNamedirective -commonNameandsubjectAltNameare separate fields - E uses
subjects:(not a real OpenSSL directive) andCN=prefixes, which are Distinguished Name components, not SAN type tags
Memory tip: Think "SAN = DNS:" - the directive name is subjectAltName, the assignment operator is =, and each value must be prefixed with its type tag (DNS:, IP:, email:) separated by commas, all on a single line.
Topics
Community Discussion
No community discussion yet for this question.