Debian Codegraph @

testenv/certs/ca-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 = "GNU Wget"
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 = "www.none.org"
72 #dns_name = "www.morethanone.org"
73
74 # A subject alternative name URI
75 #uri = "http://www.example.com"
76
77 # An IP address in case of a server.
78 #ip_address = "192.168.1.1"
79
80 # An email in case of a person
81 # email = "[email protected]"
82
83 # Challenge password used in certificate requests
84 challenge_password = 123456
85
86 # Password when encrypting a private key
87 #password = secret
88
89 # An URL that has CRLs (certificate revocation lists)
90 # available. Needed in CA certificates.
91 #crl_dist_points = "http://www.getcrl.crl/getcrl/"
92
93 # Whether this is a CA certificate or not
94 ca
95
96 # Subject Unique ID (in hex)
97 #subject_unique_id = 00153224
98
99 # Issuer Unique ID (in hex)
100 #issuer_unique_id = 00153225
101
102 #### Key usage
103
104 # The following key usage flags are used by CAs and end certificates
105
106 # Whether this certificate will be used to sign data (needed
107 # in TLS DHE ciphersuites). This is the digitalSignature flag
108 # in RFC5280 terminology.
109 # signing_key
110
111 # Whether this certificate will be used to encrypt data (needed
112 # in TLS RSA ciphersuites). Note that it is preferred to use different
113 # keys for encryption and signing. This is the keyEncipherment flag
114 # in RFC5280 terminology.
115 # encryption_key
116
117 # Whether this key will be used to sign other certificates. The
118 # keyCertSign flag in RFC5280 terminology.
119 cert_signing_key
120
121 # Whether this key will be used to sign CRLs. The
122 # cRLSign flag in RFC5280 terminology.
123 crl_signing_key
124
125 # The keyAgreement flag of RFC5280. It's purpose is loosely
126 # defined. Not use it unless required by a protocol.
127 #key_agreement
128
129 # The dataEncipherment flag of RFC5280. It's purpose is loosely
130 # defined. Not use it unless required by a protocol.
131 #data_encipherment
132
133 # The nonRepudiation flag of RFC5280. It's purpose is loosely
134 # defined. Not use it unless required by a protocol.
135 #non_repudiation
136
137 #### Extended key usage (key purposes)
138
139 # The following extensions are used in an end certificate
140 # to clarify its purpose. Some CAs also use it to indicate
141 # the types of certificates they are purposed to sign.
142
143 # Whether this certificate will be used for a TLS client;
144 # this sets the id-kp-serverAuth (1.3.6.1.5.5.7.3.1) of
145 # extended key usage.
146 #tls_www_client
147
148 # Whether this certificate will be used for a TLS server;
149 # This sets the id-kp-clientAuth (1.3.6.1.5.5.7.3.2) of
150 # extended key usage.
151 #tls_www_server
152
153 # Whether this key will be used to sign code. This sets the
154 # id-kp-codeSigning (1.3.6.1.5.5.7.3.3) of extended key usage
155 # extension.
156 #code_signing_key
157
158 # Whether this key will be used to sign OCSP data. This sets the
159 # id-kp-OCSPSigning (1.3.6.1.5.5.7.3.9) of extended key usage extension.
160 #ocsp_signing_key
161
162 # Whether this key will be used for time stamping. This sets the
163 # id-kp-timeStamping (1.3.6.1.5.5.7.3.8) of extended key usage extension.
164 #time_stamping_key
165
166 # Whether this key will be used for email protection. This sets the
167 # id-kp-emailProtection (1.3.6.1.5.5.7.3.4) of extended key usage extension.
168 #email_protection_key
169
170 # Whether this key will be used for IPsec IKE operations (1.3.6.1.5.5.7.3.17).
171 #ipsec_ike_key
172
173 ## adding custom key purpose OIDs
174
175 # for microsoft smart card logon
176 # key_purpose_oid = 1.3.6.1.4.1.311.20.2.2
177
178 # for email protection
179 # key_purpose_oid = 1.3.6.1.5.5.7.3.4
180
181 # for any purpose (must not be used in intermediate CA certificates)
182 # key_purpose_oid = 2.5.29.37.0
183
184 ### end of key purpose OIDs
185
186 # When generating a certificate from a certificate
187 # request, then honor the extensions stored in the request
188 # and store them in the real certificate.
189 honor_crq_extensions
190
191 # Path length constraint. Sets the maximum number of
192 # certificates that can be used to certify this certificate.
193 # (i.e. the certificate chain length)
194 #path_len = -1
195 #path_len = 2
196
197 # OCSP URI
198 # ocsp_uri = http://my.ocsp.server/ocsp
199
200 # CA issuers URI
201 # ca_issuers_uri = http://my.ca.issuer
202
203 # Certificate policies
204 #policy1 = 1.3.6.1.4.1.5484.1.10.99.1.0
205 #policy1_txt = "This is a long policy to summarize"
206 #policy1_url = http://www.example.com/a-policy-to-read
207
208 #policy2 = 1.3.6.1.4.1.5484.1.10.99.1.1
209 #policy2_txt = "This is a short policy"
210 #policy2_url = http://www.example.com/another-policy-to-read
211
212 # Name constraints
213
214 # DNS
215 #nc_permit_dns = example.com
216 #nc_exclude_dns = test.example.com
217
218 # EMAIL
219 #nc_permit_email = "[email protected]"
220
221 # Exclude subdomains of example.com
222 #nc_exclude_email = .example.com
223
224 # Exclude all e-mail addresses of example.com
225 #nc_exclude_email = example.com
226
227 # Options for proxy certificates
228 #proxy_policy_language = 1.3.6.1.5.5.7.21.1
229
230 # Options for generating a CRL
231
232 # The number of days the next CRL update will be due.
233 # next CRL update will be in 43 days
234 #crl_next_update = 43
235
236 # this is the 5th CRL by this CA
237 # Comment the field for a time-based number.
238 #crl_number = 5
239
240 # Specify the update dates more precisely.
241 #crl_this_update_date = "2004-02-29 16:21:42"
242 #crl_next_update_date = "2025-02-29 16:24:41"
243
244 # The date that the certificates will be made seen as
245 # being revoked.
246 #crl_revocation_date = "2025-02-29 16:24:41"