Debian Codegraph @

testenv/certs/server-template.cfg

raw
1 # X.509 Certificate options
2 #
3 # DN options
4
5 # The organization of the subject.
6 organization = "GNU"
7
8 # The organizational unit of the subject.
9 unit = "Wget"
10
11 # The locality of the subject.
12 # locality =
13
14 # The state of the certificate owner.
15 # state = ""
16
17 # The country of the subject. Two letter code.
18 # country = GR
19
20 # The common name of the certificate owner.
21 cn = "127.0.0.1"
22
23 # A user id of the certificate owner.
24 #uid = ""
25
26 # Set domain components
27 #dc = "name"
28 #dc = "domain"
29
30 # If the supported DN OIDs are not adequate you can set
31 # any OID here.
32 # For example set the X.520 Title and the X.520 Pseudonym
33 # by using OID and string pairs.
34 #dn_oid = 2.5.4.12 Dr.
35 #dn_oid = 2.5.4.65 jackal
36
37 # This is deprecated and should not be used in new
38 # certificates.
39 # pkcs9_email = "[email protected]"
40
41 # An alternative way to set the certificate's distinguished name directly
42 # is with the "dn" option. The attribute names allowed are:
43 # C (country), street, O (organization), OU (unit), title, CN (common name),
44 # L (locality), ST (state), placeOfBirth, gender, countryOfCitizenship,
45 # countryOfResidence, serialNumber, telephoneNumber, surName, initials,
46 # generationQualifier, givenName, pseudonym, dnQualifier, postalCode, name,
47 # businessCategory, DC, UID, jurisdictionOfIncorporationLocalityName,
48 # jurisdictionOfIncorporationStateOrProvinceName,
49 # jurisdictionOfIncorporationCountryName, XmppAddr, and numeric OIDs.
50
51 #dn = "cn = Nikos,st = New Something,C=GR,surName=Mavrogiannopoulos,2.5.4.9=Arkadias"
52
53 # The serial number of the certificate
54 # Comment the field for a time-based serial number.
55 # serial = 007
56
57 # In how many days, counting from today, this certificate will expire.
58 # Use -1 if there is no expiration date.
59 expiration_days = -1
60
61 # Alternatively you may set concrete dates and time. The GNU date string
62 # formats are accepted. See:
63 # http://www.gnu.org/software/tar/manual/html_node/Date-input-formats.html
64
65 #activation_date = "2004-02-29 16:21:42"
66 #expiration_date = "2025-02-29 16:24:41"
67
68 # X.509 v3 extensions
69
70 # A dnsname in case of a WWW server.
71 dns_name = "localhost"
72
73 # A subject alternative name URI
74 #uri = "http://www.example.com"
75
76 # An IP address in case of a server.
77 # ip_address = "127.0.0.1"
78
79 # An email in case of a person
80 # email = "[email protected]"
81
82 # Challenge password used in certificate requests
83 challenge_password = 123456
84
85 # Password when encrypting a private key
86 #password = secret
87
88 # An URL that has CRLs (certificate revocation lists)
89 # available. Needed in CA certificates.
90 #crl_dist_points = "http://www.getcrl.crl/getcrl/"
91
92 # Whether this is a CA certificate or not
93 # ca
94
95 # Subject Unique ID (in hex)
96 #subject_unique_id = 00153224
97
98 # Issuer Unique ID (in hex)
99 #issuer_unique_id = 00153225
100
101 #### Key usage
102
103 # The following key usage flags are used by CAs and end certificates
104
105 # Whether this certificate will be used to sign data (needed
106 # in TLS DHE ciphersuites). This is the digitalSignature flag
107 # in RFC5280 terminology.
108 signing_key
109
110 # Whether this certificate will be used to encrypt data (needed
111 # in TLS RSA ciphersuites). Note that it is preferred to use different
112 # keys for encryption and signing. This is the keyEncipherment flag
113 # in RFC5280 terminology.
114 encryption_key
115
116 # Whether this key will be used to sign other certificates. The
117 # keyCertSign flag in RFC5280 terminology.
118 # cert_signing_key
119
120 # Whether this key will be used to sign CRLs. The
121 # cRLSign flag in RFC5280 terminology.
122 # crl_signing_key
123
124 # The keyAgreement flag of RFC5280. It's purpose is loosely
125 # defined. Not use it unless required by a protocol.
126 #key_agreement
127
128 # The dataEncipherment flag of RFC5280. It's purpose is loosely
129 # defined. Not use it unless required by a protocol.
130 #data_encipherment
131
132 # The nonRepudiation flag of RFC5280. It's purpose is loosely
133 # defined. Not use it unless required by a protocol.
134 #non_repudiation
135
136 #### Extended key usage (key purposes)
137
138 # The following extensions are used in an end certificate
139 # to clarify its purpose. Some CAs also use it to indicate
140 # the types of certificates they are purposed to sign.
141
142 # Whether this certificate will be used for a TLS client;
143 # this sets the id-kp-serverAuth (1.3.6.1.5.5.7.3.1) of
144 # extended key usage.
145 #tls_www_client
146
147 # Whether this certificate will be used for a TLS server;
148 # This sets the id-kp-clientAuth (1.3.6.1.5.5.7.3.2) of
149 # extended key usage.
150 tls_www_server
151
152 # Whether this key will be used to sign code. This sets the
153 # id-kp-codeSigning (1.3.6.1.5.5.7.3.3) of extended key usage
154 # extension.
155 #code_signing_key
156
157 # Whether this key will be used to sign OCSP data. This sets the
158 # id-kp-OCSPSigning (1.3.6.1.5.5.7.3.9) of extended key usage extension.
159 #ocsp_signing_key
160
161 # Whether this key will be used for time stamping. This sets the
162 # id-kp-timeStamping (1.3.6.1.5.5.7.3.8) of extended key usage extension.
163 #time_stamping_key
164
165 # Whether this key will be used for email protection. This sets the
166 # id-kp-emailProtection (1.3.6.1.5.5.7.3.4) of extended key usage extension.
167 #email_protection_key
168
169 # Whether this key will be used for IPsec IKE operations (1.3.6.1.5.5.7.3.17).
170 #ipsec_ike_key
171
172 ## adding custom key purpose OIDs
173
174 # for microsoft smart card logon
175 # key_purpose_oid = 1.3.6.1.4.1.311.20.2.2
176
177 # for email protection
178 # key_purpose_oid = 1.3.6.1.5.5.7.3.4
179
180 # for any purpose (must not be used in intermediate CA certificates)
181 # key_purpose_oid = 2.5.29.37.0
182
183 ### end of key purpose OIDs
184
185 # When generating a certificate from a certificate
186 # request, then honor the extensions stored in the request
187 # and store them in the real certificate.
188 honor_crq_extensions
189
190 # Path length constraint. Sets the maximum number of
191 # certificates that can be used to certify this certificate.
192 # (i.e. the certificate chain length)
193 #path_len = -1
194 #path_len = 2
195
196 # OCSP URI
197 # ocsp_uri = http://my.ocsp.server/ocsp
198
199 # CA issuers URI
200 # ca_issuers_uri = http://my.ca.issuer
201
202 # Certificate policies
203 #policy1 = 1.3.6.1.4.1.5484.1.10.99.1.0
204 #policy1_txt = "This is a long policy to summarize"
205 #policy1_url = http://www.example.com/a-policy-to-read
206
207 #policy2 = 1.3.6.1.4.1.5484.1.10.99.1.1
208 #policy2_txt = "This is a short policy"
209 #policy2_url = http://www.example.com/another-policy-to-read
210
211 # Name constraints
212
213 # DNS
214 #nc_permit_dns = example.com
215 #nc_exclude_dns = test.example.com
216
217 # EMAIL
218 #nc_permit_email = "[email protected]"
219
220 # Exclude subdomains of example.com
221 #nc_exclude_email = .example.com
222
223 # Exclude all e-mail addresses of example.com
224 #nc_exclude_email = example.com
225
226 # Options for proxy certificates
227 #proxy_policy_language = 1.3.6.1.5.5.7.21.1
228
229 # Options for generating a CRL
230
231 # The number of days the next CRL update will be due.
232 # next CRL update will be in 43 days
233 #crl_next_update = 43
234
235 # this is the 5th CRL by this CA
236 # Comment the field for a time-based number.
237 #crl_number = 5
238
239 # Specify the update dates more precisely.
240 #crl_this_update_date = "2004-02-29 16:21:42"
241 #crl_next_update_date = "2025-02-29 16:24:41"
242
243 # The date that the certificates will be made seen as
244 # being revoked.
245 #crl_revocation_date = "2025-02-29 16:24:41"