]>
Commit | Line | Data |
---|---|---|
3b0168a6 AM |
1 | diff -urN openssl-1.0.1f.org/doc/apps/cms.pod openssl-1.0.1f/doc/apps/cms.pod |
2 | --- openssl-1.0.1f.org/doc/apps/cms.pod 2014-01-06 14:47:42.000000000 +0100 | |
3 | +++ openssl-1.0.1f/doc/apps/cms.pod 2014-01-19 01:10:11.205967419 +0100 | |
4 | @@ -450,28 +450,28 @@ | |
5 | ||
6 | =over 4 | |
7 | ||
8 | -=item 0 | |
9 | +=item C<0> | |
10 | ||
11 | the operation was completely successfully. | |
12 | ||
13 | -=item 1 | |
14 | +=item C<1> | |
15 | ||
16 | an error occurred parsing the command options. | |
17 | ||
18 | -=item 2 | |
19 | +=item C<2> | |
20 | ||
21 | one of the input files could not be read. | |
22 | ||
23 | -=item 3 | |
24 | +=item C<3> | |
25 | ||
26 | an error occurred creating the CMS file or when reading the MIME | |
27 | message. | |
28 | ||
29 | -=item 4 | |
30 | +=item C<4> | |
31 | ||
32 | an error occurred decrypting or verifying the message. | |
33 | ||
34 | -=item 5 | |
35 | +=item C<5> | |
36 | ||
37 | the message was verified correctly but an error occurred writing out | |
38 | the signers certificates. | |
39 | diff -urN openssl-1.0.1f.org/doc/apps/smime.pod openssl-1.0.1f/doc/apps/smime.pod | |
40 | --- openssl-1.0.1f.org/doc/apps/smime.pod 2014-01-06 14:47:42.000000000 +0100 | |
41 | +++ openssl-1.0.1f/doc/apps/smime.pod 2014-01-19 01:10:11.229301529 +0100 | |
42 | @@ -308,28 +308,28 @@ | |
43 | ||
44 | =over 4 | |
45 | ||
46 | -=item 0 | |
47 | +=item C<0> | |
48 | ||
49 | the operation was completely successfully. | |
50 | ||
51 | -=item 1 | |
52 | +=item C<1> | |
53 | ||
54 | an error occurred parsing the command options. | |
55 | ||
56 | -=item 2 | |
57 | +=item C<2> | |
58 | ||
59 | one of the input files could not be read. | |
60 | ||
61 | -=item 3 | |
62 | +=item C<3> | |
63 | ||
64 | an error occurred creating the PKCS#7 file or when reading the MIME | |
65 | message. | |
66 | ||
67 | -=item 4 | |
68 | +=item C<4> | |
69 | ||
70 | an error occurred decrypting or verifying the message. | |
71 | ||
72 | -=item 5 | |
73 | +=item C<5> | |
74 | ||
75 | the message was verified correctly but an error occurred writing out | |
76 | the signers certificates. | |
77 | diff -urN openssl-1.0.1f.org/doc/apps/ts.pod openssl-1.0.1f/doc/apps/ts.pod | |
78 | --- openssl-1.0.1f.org/doc/apps/ts.pod 2014-01-06 14:47:42.000000000 +0100 | |
79 | +++ openssl-1.0.1f/doc/apps/ts.pod 2014-01-19 01:10:11.239301862 +0100 | |
80 | @@ -58,19 +58,19 @@ | |
81 | ||
82 | =over 4 | |
83 | ||
84 | -=item 1. | |
85 | +=item C<1>. | |
86 | ||
87 | The TSA client computes a one-way hash value for a data file and sends | |
88 | the hash to the TSA. | |
89 | ||
90 | -=item 2. | |
91 | +=item C<2>. | |
92 | ||
93 | The TSA attaches the current date and time to the received hash value, | |
94 | signs them and sends the time stamp token back to the client. By | |
95 | creating this token the TSA certifies the existence of the original | |
96 | data file at the time of response generation. | |
97 | ||
98 | -=item 3. | |
99 | +=item C<3>. | |
100 | ||
101 | The TSA client receives the time stamp token and verifies the | |
102 | signature on it. It also checks if the token contains the same hash | |
103 | diff -urN openssl-1.0.1f.org/doc/crypto/rand.pod openssl-1.0.1f/doc/crypto/rand.pod | |
104 | --- openssl-1.0.1f.org/doc/crypto/rand.pod 2014-01-06 14:47:42.000000000 +0100 | |
105 | +++ openssl-1.0.1f/doc/crypto/rand.pod 2014-01-19 01:10:11.382639970 +0100 | |
106 | @@ -74,16 +74,16 @@ | |
107 | ||
108 | =over 4 | |
109 | ||
110 | -=item 1 | |
111 | +=item C<1> | |
112 | ||
113 | A good hashing algorithm to mix things up and to convert the RNG 'state' | |
114 | to random numbers. | |
115 | ||
116 | -=item 2 | |
117 | +=item C<2> | |
118 | ||
119 | An initial source of random 'state'. | |
120 | ||
121 | -=item 3 | |
122 | +=item C<3> | |
123 | ||
124 | The state should be very large. If the RNG is being used to generate | |
125 | 4096 bit RSA keys, 2 2048 bit random strings are required (at a minimum). | |
126 | @@ -93,13 +93,13 @@ | |
127 | a bad idea to keep quite a lot of RNG state. It should be easier to | |
128 | break a cipher than guess the RNG seed data. | |
129 | ||
130 | -=item 4 | |
131 | +=item C<4> | |
132 | ||
133 | Any RNG seed data should influence all subsequent random numbers | |
134 | generated. This implies that any random seed data entered will have | |
135 | an influence on all subsequent random numbers generated. | |
136 | ||
137 | -=item 5 | |
138 | +=item C<5> | |
139 | ||
140 | When using data to seed the RNG state, the data used should not be | |
141 | extractable from the RNG state. I believe this should be a | |
142 | @@ -108,12 +108,12 @@ | |
143 | not be disclosed by either subsequent random numbers or a | |
144 | 'core' dump left by a program crash. | |
145 | ||
146 | -=item 6 | |
147 | +=item C<6> | |
148 | ||
149 | Given the same initial 'state', 2 systems should deviate in their RNG state | |
150 | (and hence the random numbers generated) over time if at all possible. | |
151 | ||
152 | -=item 7 | |
153 | +=item C<7> | |
154 | ||
155 | Given the random number output stream, it should not be possible to determine | |
156 | the RNG state or the next random number. | |
157 | diff -urN openssl-1.0.1f.org/doc/ssl/SSL_accept.pod openssl-1.0.1f/doc/ssl/SSL_accept.pod | |
158 | --- openssl-1.0.1f.org/doc/ssl/SSL_accept.pod 2014-01-06 14:47:42.000000000 +0100 | |
159 | +++ openssl-1.0.1f/doc/ssl/SSL_accept.pod 2014-01-19 01:10:11.409307524 +0100 | |
160 | @@ -44,13 +44,13 @@ | |
161 | ||
162 | =over 4 | |
163 | ||
164 | -=item 0 | |
165 | +=item C<0> | |
166 | ||
167 | The TLS/SSL handshake was not successful but was shut down controlled and | |
168 | by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the | |
169 | return value B<ret> to find out the reason. | |
170 | ||
171 | -=item 1 | |
172 | +=item C<1> | |
173 | ||
174 | The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been | |
175 | established. | |
176 | diff -urN openssl-1.0.1f.org/doc/ssl/SSL_clear.pod openssl-1.0.1f/doc/ssl/SSL_clear.pod | |
177 | --- openssl-1.0.1f.org/doc/ssl/SSL_clear.pod 2014-01-06 14:47:42.000000000 +0100 | |
178 | +++ openssl-1.0.1f/doc/ssl/SSL_clear.pod 2014-01-19 01:10:11.415974413 +0100 | |
179 | @@ -56,12 +56,12 @@ | |
180 | ||
181 | =over 4 | |
182 | ||
183 | -=item 0 | |
184 | +=item C<0> | |
185 | ||
186 | The SSL_clear() operation could not be performed. Check the error stack to | |
187 | find out the reason. | |
188 | ||
189 | -=item 1 | |
190 | +=item C<1> | |
191 | ||
192 | The SSL_clear() operation was successful. | |
193 | ||
194 | diff -urN openssl-1.0.1f.org/doc/ssl/SSL_COMP_add_compression_method.pod openssl-1.0.1f/doc/ssl/SSL_COMP_add_compression_method.pod | |
195 | --- openssl-1.0.1f.org/doc/ssl/SSL_COMP_add_compression_method.pod 2014-01-06 14:47:42.000000000 +0100 | |
196 | +++ openssl-1.0.1f/doc/ssl/SSL_COMP_add_compression_method.pod 2014-01-19 01:10:11.415974413 +0100 | |
197 | @@ -53,11 +53,11 @@ | |
198 | ||
199 | =over 4 | |
200 | ||
201 | -=item 0 | |
202 | +=item C<0> | |
203 | ||
204 | The operation succeeded. | |
205 | ||
206 | -=item 1 | |
207 | +=item C<1> | |
208 | ||
209 | The operation failed. Check the error queue to find out the reason. | |
210 | ||
211 | diff -urN openssl-1.0.1f.org/doc/ssl/SSL_connect.pod openssl-1.0.1f/doc/ssl/SSL_connect.pod | |
212 | --- openssl-1.0.1f.org/doc/ssl/SSL_connect.pod 2014-01-06 14:47:42.000000000 +0100 | |
213 | +++ openssl-1.0.1f/doc/ssl/SSL_connect.pod 2014-01-19 01:10:11.415974413 +0100 | |
214 | @@ -41,13 +41,13 @@ | |
215 | ||
216 | =over 4 | |
217 | ||
218 | -=item 0 | |
219 | +=item C<0> | |
220 | ||
221 | The TLS/SSL handshake was not successful but was shut down controlled and | |
222 | by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the | |
223 | return value B<ret> to find out the reason. | |
224 | ||
225 | -=item 1 | |
226 | +=item C<1> | |
227 | ||
228 | The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been | |
229 | established. | |
230 | diff -urN openssl-1.0.1f.org/doc/ssl/SSL_CTX_add_session.pod openssl-1.0.1f/doc/ssl/SSL_CTX_add_session.pod | |
231 | --- openssl-1.0.1f.org/doc/ssl/SSL_CTX_add_session.pod 2014-01-06 14:47:42.000000000 +0100 | |
232 | +++ openssl-1.0.1f/doc/ssl/SSL_CTX_add_session.pod 2014-01-19 01:10:11.419307858 +0100 | |
233 | @@ -52,13 +52,13 @@ | |
234 | ||
235 | =over 4 | |
236 | ||
237 | -=item 0 | |
238 | +=item C<0> | |
239 | ||
240 | The operation failed. In case of the add operation, it was tried to add | |
241 | the same (identical) session twice. In case of the remove operation, the | |
242 | session was not found in the cache. | |
243 | ||
244 | -=item 1 | |
245 | +=item C<1> | |
246 | ||
247 | The operation succeeded. | |
248 | ||
249 | diff -urN openssl-1.0.1f.org/doc/ssl/SSL_CTX_load_verify_locations.pod openssl-1.0.1f/doc/ssl/SSL_CTX_load_verify_locations.pod | |
250 | --- openssl-1.0.1f.org/doc/ssl/SSL_CTX_load_verify_locations.pod 2014-01-06 14:47:42.000000000 +0100 | |
251 | +++ openssl-1.0.1f/doc/ssl/SSL_CTX_load_verify_locations.pod 2014-01-19 01:10:11.422641302 +0100 | |
252 | @@ -100,13 +100,13 @@ | |
253 | ||
254 | =over 4 | |
255 | ||
256 | -=item 0 | |
257 | +=item C<0> | |
258 | ||
259 | The operation failed because B<CAfile> and B<CApath> are NULL or the | |
260 | processing at one of the locations specified failed. Check the error | |
261 | stack to find out the reason. | |
262 | ||
263 | -=item 1 | |
264 | +=item C<1> | |
265 | ||
266 | The operation succeeded. | |
267 | ||
268 | diff -urN openssl-1.0.1f.org/doc/ssl/SSL_CTX_set_client_CA_list.pod openssl-1.0.1f/doc/ssl/SSL_CTX_set_client_CA_list.pod | |
269 | --- openssl-1.0.1f.org/doc/ssl/SSL_CTX_set_client_CA_list.pod 2014-01-06 14:47:42.000000000 +0100 | |
270 | +++ openssl-1.0.1f/doc/ssl/SSL_CTX_set_client_CA_list.pod 2014-01-19 01:10:11.429308190 +0100 | |
271 | @@ -66,13 +66,13 @@ | |
272 | ||
273 | =over 4 | |
274 | ||
275 | -=item 0 | |
276 | +=item C<0> | |
277 | ||
278 | A failure while manipulating the STACK_OF(X509_NAME) object occurred or | |
279 | the X509_NAME could not be extracted from B<cacert>. Check the error stack | |
280 | to find out the reason. | |
281 | ||
282 | -=item 1 | |
283 | +=item C<1> | |
284 | ||
285 | The operation succeeded. | |
286 | ||
287 | diff -urN openssl-1.0.1f.org/doc/ssl/SSL_CTX_set_session_id_context.pod openssl-1.0.1f/doc/ssl/SSL_CTX_set_session_id_context.pod | |
288 | --- openssl-1.0.1f.org/doc/ssl/SSL_CTX_set_session_id_context.pod 2014-01-06 14:47:42.000000000 +0100 | |
289 | +++ openssl-1.0.1f/doc/ssl/SSL_CTX_set_session_id_context.pod 2014-01-19 01:10:11.439308524 +0100 | |
290 | @@ -64,13 +64,13 @@ | |
291 | ||
292 | =over 4 | |
293 | ||
294 | -=item 0 | |
295 | +=item C<0> | |
296 | ||
297 | The length B<sid_ctx_len> of the session id context B<sid_ctx> exceeded | |
298 | the maximum allowed length of B<SSL_MAX_SSL_SESSION_ID_LENGTH>. The error | |
299 | is logged to the error stack. | |
300 | ||
301 | -=item 1 | |
302 | +=item C<1> | |
303 | ||
304 | The operation succeeded. | |
305 | ||
306 | diff -urN openssl-1.0.1f.org/doc/ssl/SSL_CTX_set_ssl_version.pod openssl-1.0.1f/doc/ssl/SSL_CTX_set_ssl_version.pod | |
307 | --- openssl-1.0.1f.org/doc/ssl/SSL_CTX_set_ssl_version.pod 2014-01-06 14:47:42.000000000 +0100 | |
308 | +++ openssl-1.0.1f/doc/ssl/SSL_CTX_set_ssl_version.pod 2014-01-19 01:10:11.439308524 +0100 | |
309 | @@ -42,11 +42,11 @@ | |
310 | ||
311 | =over 4 | |
312 | ||
313 | -=item 0 | |
314 | +=item C<0> | |
315 | ||
316 | The new choice failed, check the error stack to find out the reason. | |
317 | ||
318 | -=item 1 | |
319 | +=item C<1> | |
320 | ||
321 | The operation succeeded. | |
322 | ||
323 | diff -urN openssl-1.0.1f.org/doc/ssl/SSL_CTX_use_psk_identity_hint.pod openssl-1.0.1f/doc/ssl/SSL_CTX_use_psk_identity_hint.pod | |
324 | --- openssl-1.0.1f.org/doc/ssl/SSL_CTX_use_psk_identity_hint.pod 2014-01-06 14:47:42.000000000 +0100 | |
325 | +++ openssl-1.0.1f/doc/ssl/SSL_CTX_use_psk_identity_hint.pod 2014-01-19 01:10:11.445975412 +0100 | |
326 | @@ -96,7 +96,7 @@ | |
327 | connection will fail with decryption_error before it will be finished | |
328 | completely. | |
329 | ||
330 | -=item 0 | |
331 | +=item C<0> | |
332 | ||
333 | PSK identity was not found. An "unknown_psk_identity" alert message | |
334 | will be sent and the connection setup fails. | |
335 | diff -urN openssl-1.0.1f.org/doc/ssl/SSL_do_handshake.pod openssl-1.0.1f/doc/ssl/SSL_do_handshake.pod | |
336 | --- openssl-1.0.1f.org/doc/ssl/SSL_do_handshake.pod 2014-01-06 14:47:42.000000000 +0100 | |
337 | +++ openssl-1.0.1f/doc/ssl/SSL_do_handshake.pod 2014-01-19 01:10:11.445975412 +0100 | |
338 | @@ -45,13 +45,13 @@ | |
339 | ||
340 | =over 4 | |
341 | ||
342 | -=item 0 | |
343 | +=item C<0> | |
344 | ||
345 | The TLS/SSL handshake was not successful but was shut down controlled and | |
346 | by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the | |
347 | return value B<ret> to find out the reason. | |
348 | ||
349 | -=item 1 | |
350 | +=item C<1> | |
351 | ||
352 | The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been | |
353 | established. | |
354 | diff -urN openssl-1.0.1f.org/doc/ssl/SSL_read.pod openssl-1.0.1f/doc/ssl/SSL_read.pod | |
355 | --- openssl-1.0.1f.org/doc/ssl/SSL_read.pod 2014-01-06 14:47:42.000000000 +0100 | |
356 | +++ openssl-1.0.1f/doc/ssl/SSL_read.pod 2014-01-19 01:10:11.459309190 +0100 | |
357 | @@ -86,7 +86,7 @@ | |
358 | The read operation was successful; the return value is the number of | |
359 | bytes actually read from the TLS/SSL connection. | |
360 | ||
361 | -=item 0 | |
362 | +=item C<0> | |
363 | ||
364 | The read operation was not successful. The reason may either be a clean | |
365 | shutdown due to a "close notify" alert sent by the peer (in which case | |
366 | diff -urN openssl-1.0.1f.org/doc/ssl/SSL_session_reused.pod openssl-1.0.1f/doc/ssl/SSL_session_reused.pod | |
367 | --- openssl-1.0.1f.org/doc/ssl/SSL_session_reused.pod 2014-01-06 14:47:42.000000000 +0100 | |
368 | +++ openssl-1.0.1f/doc/ssl/SSL_session_reused.pod 2014-01-19 01:10:11.465976078 +0100 | |
369 | @@ -27,11 +27,11 @@ | |
370 | ||
371 | =over 4 | |
372 | ||
373 | -=item 0 | |
374 | +=item C<0> | |
375 | ||
376 | A new session was negotiated. | |
377 | ||
378 | -=item 1 | |
379 | +=item C<1> | |
380 | ||
381 | A session was reused. | |
382 | ||
383 | diff -urN openssl-1.0.1f.org/doc/ssl/SSL_set_fd.pod openssl-1.0.1f/doc/ssl/SSL_set_fd.pod | |
384 | --- openssl-1.0.1f.org/doc/ssl/SSL_set_fd.pod 2014-01-06 14:47:42.000000000 +0100 | |
385 | +++ openssl-1.0.1f/doc/ssl/SSL_set_fd.pod 2014-01-19 01:10:11.469309522 +0100 | |
386 | @@ -35,11 +35,11 @@ | |
387 | ||
388 | =over 4 | |
389 | ||
390 | -=item 0 | |
391 | +=item C<0> | |
392 | ||
393 | The operation failed. Check the error stack to find out why. | |
394 | ||
395 | -=item 1 | |
396 | +=item C<1> | |
397 | ||
398 | The operation succeeded. | |
399 | ||
400 | diff -urN openssl-1.0.1f.org/doc/ssl/SSL_set_session.pod openssl-1.0.1f/doc/ssl/SSL_set_session.pod | |
401 | --- openssl-1.0.1f.org/doc/ssl/SSL_set_session.pod 2014-01-06 14:47:42.000000000 +0100 | |
402 | +++ openssl-1.0.1f/doc/ssl/SSL_set_session.pod 2014-01-19 01:10:11.469309522 +0100 | |
403 | @@ -37,11 +37,11 @@ | |
404 | ||
405 | =over 4 | |
406 | ||
407 | -=item 0 | |
408 | +=item C<0> | |
409 | ||
410 | The operation failed; check the error stack to find out the reason. | |
411 | ||
412 | -=item 1 | |
413 | +=item C<1> | |
414 | ||
415 | The operation succeeded. | |
416 | ||
3b0168a6 AM |
417 | diff -urN openssl-1.0.1f.org/doc/ssl/SSL_shutdown.pod openssl-1.0.1f/doc/ssl/SSL_shutdown.pod |
418 | --- openssl-1.0.1f.org/doc/ssl/SSL_shutdown.pod 2014-01-06 14:47:42.000000000 +0100 | |
419 | +++ openssl-1.0.1f/doc/ssl/SSL_shutdown.pod 2014-01-19 01:10:11.469309522 +0100 | |
420 | @@ -92,14 +92,14 @@ | |
421 | ||
422 | =over 4 | |
423 | ||
424 | -=item 0 | |
425 | +=item C<0> | |
426 | ||
427 | The shutdown is not yet finished. Call SSL_shutdown() for a second time, | |
428 | if a bidirectional shutdown shall be performed. | |
429 | The output of L<SSL_get_error(3)|SSL_get_error(3)> may be misleading, as an | |
430 | erroneous SSL_ERROR_SYSCALL may be flagged even though no error occurred. | |
431 | ||
432 | -=item 1 | |
433 | +=item C<1> | |
434 | ||
435 | The shutdown was successfully completed. The "close notify" alert was sent | |
436 | and the peer's "close notify" alert was received. | |
437 | diff -urN openssl-1.0.1f.org/doc/ssl/SSL_write.pod openssl-1.0.1f/doc/ssl/SSL_write.pod | |
438 | --- openssl-1.0.1f.org/doc/ssl/SSL_write.pod 2014-01-06 14:47:42.000000000 +0100 | |
439 | +++ openssl-1.0.1f/doc/ssl/SSL_write.pod 2014-01-19 01:10:11.475976412 +0100 | |
440 | @@ -79,7 +79,7 @@ | |
441 | The write operation was successful, the return value is the number of | |
442 | bytes actually written to the TLS/SSL connection. | |
443 | ||
444 | -=item 0 | |
445 | +=item C<0> | |
446 | ||
447 | The write operation was not successful. Probably the underlying connection | |
448 | was closed. Call SSL_get_error() with the return value B<ret> to find out, |