6 | 6 |
Bug-Debian: http://bugs.debian.org/723954
|
7 | 7 |
Bug: http://rt.openssl.org/Ticket/Display.html?id=3146&user=guest&pass=guest
|
8 | 8 |
|
9 | |
--- openssl-1.0.1e.orig/doc/apps/smime.pod
|
10 | |
+++ openssl-1.0.1e/doc/apps/smime.pod
|
11 | |
@@ -308,28 +308,28 @@ remains DER.
|
|
9 |
Index: openssl-1.0.1e/doc/apps/smime.pod
|
|
10 |
===================================================================
|
|
11 |
--- openssl-1.0.1e.orig/doc/apps/smime.pod 2013-12-22 17:21:52.913435572 +0100
|
|
12 |
+++ openssl-1.0.1e/doc/apps/smime.pod 2013-12-22 17:21:52.909435656 +0100
|
|
13 |
@@ -308,28 +308,28 @@
|
12 | 14 |
|
13 | 15 |
=over 4
|
14 | 16 |
|
|
43 | 45 |
|
44 | 46 |
the message was verified correctly but an error occurred writing out
|
45 | 47 |
the signers certificates.
|
46 | |
--- openssl-1.0.1e.orig/doc/apps/cms.pod
|
47 | |
+++ openssl-1.0.1e/doc/apps/cms.pod
|
48 | |
@@ -450,28 +450,28 @@ remains DER.
|
|
48 |
Index: openssl-1.0.1e/doc/apps/cms.pod
|
|
49 |
===================================================================
|
|
50 |
--- openssl-1.0.1e.orig/doc/apps/cms.pod 2013-12-22 17:21:52.913435572 +0100
|
|
51 |
+++ openssl-1.0.1e/doc/apps/cms.pod 2013-12-22 17:21:52.909435656 +0100
|
|
52 |
@@ -450,28 +450,28 @@
|
49 | 53 |
|
50 | 54 |
=over 4
|
51 | 55 |
|
|
80 | 84 |
|
81 | 85 |
the message was verified correctly but an error occurred writing out
|
82 | 86 |
the signers certificates.
|
83 | |
--- openssl-1.0.1e.orig/doc/ssl/SSL_clear.pod
|
84 | |
+++ openssl-1.0.1e/doc/ssl/SSL_clear.pod
|
85 | |
@@ -56,12 +56,12 @@ The following return values can occur:
|
|
87 |
Index: openssl-1.0.1e/doc/ssl/SSL_clear.pod
|
|
88 |
===================================================================
|
|
89 |
--- openssl-1.0.1e.orig/doc/ssl/SSL_clear.pod 2013-12-22 17:21:52.913435572 +0100
|
|
90 |
+++ openssl-1.0.1e/doc/ssl/SSL_clear.pod 2013-12-22 17:21:52.909435656 +0100
|
|
91 |
@@ -56,12 +56,12 @@
|
86 | 92 |
|
87 | 93 |
=over 4
|
88 | 94 |
|
|
97 | 103 |
|
98 | 104 |
The SSL_clear() operation was successful.
|
99 | 105 |
|
100 | |
--- openssl-1.0.1e.orig/doc/ssl/SSL_session_reused.pod
|
101 | |
+++ openssl-1.0.1e/doc/ssl/SSL_session_reused.pod
|
102 | |
@@ -27,11 +27,11 @@ The following return values can occur:
|
|
106 |
Index: openssl-1.0.1e/doc/ssl/SSL_session_reused.pod
|
|
107 |
===================================================================
|
|
108 |
--- openssl-1.0.1e.orig/doc/ssl/SSL_session_reused.pod 2013-12-22 17:21:52.913435572 +0100
|
|
109 |
+++ openssl-1.0.1e/doc/ssl/SSL_session_reused.pod 2013-12-22 17:21:52.909435656 +0100
|
|
110 |
@@ -27,11 +27,11 @@
|
103 | 111 |
|
104 | 112 |
=over 4
|
105 | 113 |
|
|
113 | 121 |
|
114 | 122 |
A session was reused.
|
115 | 123 |
|
116 | |
--- openssl-1.0.1e.orig/doc/ssl/SSL_set_session.pod
|
117 | |
+++ openssl-1.0.1e/doc/ssl/SSL_set_session.pod
|
118 | |
@@ -37,11 +37,11 @@ The following return values can occur:
|
|
124 |
Index: openssl-1.0.1e/doc/ssl/SSL_set_session.pod
|
|
125 |
===================================================================
|
|
126 |
--- openssl-1.0.1e.orig/doc/ssl/SSL_set_session.pod 2013-12-22 17:21:52.913435572 +0100
|
|
127 |
+++ openssl-1.0.1e/doc/ssl/SSL_set_session.pod 2013-12-22 17:21:52.909435656 +0100
|
|
128 |
@@ -37,11 +37,11 @@
|
119 | 129 |
|
120 | 130 |
=over 4
|
121 | 131 |
|
|
129 | 139 |
|
130 | 140 |
The operation succeeded.
|
131 | 141 |
|
132 | |
--- openssl-1.0.1e.orig/doc/ssl/SSL_connect.pod
|
133 | |
+++ openssl-1.0.1e/doc/ssl/SSL_connect.pod
|
134 | |
@@ -49,13 +49,13 @@ not clean. It can also occur of action i
|
135 | |
for non-blocking BIOs. Call SSL_get_error() with the return value B<ret>
|
136 | |
to find out the reason.
|
|
142 |
Index: openssl-1.0.1e/doc/ssl/SSL_connect.pod
|
|
143 |
===================================================================
|
|
144 |
--- openssl-1.0.1e.orig/doc/ssl/SSL_connect.pod 2013-12-22 17:21:52.913435572 +0100
|
|
145 |
+++ openssl-1.0.1e/doc/ssl/SSL_connect.pod 2013-12-22 17:22:42.956402467 +0100
|
|
146 |
@@ -41,13 +41,13 @@
|
|
147 |
|
|
148 |
=over 4
|
137 | 149 |
|
138 | 150 |
-=item 0
|
139 | 151 |
+=item C<0>
|
|
147 | 159 |
|
148 | 160 |
The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
|
149 | 161 |
established.
|
150 | |
--- openssl-1.0.1e.orig/doc/ssl/SSL_shutdown.pod
|
151 | |
+++ openssl-1.0.1e/doc/ssl/SSL_shutdown.pod
|
152 | |
@@ -92,7 +92,7 @@ The following return values can occur:
|
153 | |
|
154 | |
=over 4
|
|
162 |
Index: openssl-1.0.1e/doc/ssl/SSL_shutdown.pod
|
|
163 |
===================================================================
|
|
164 |
--- openssl-1.0.1e.orig/doc/ssl/SSL_shutdown.pod 2013-12-22 17:21:52.913435572 +0100
|
|
165 |
+++ openssl-1.0.1e/doc/ssl/SSL_shutdown.pod 2013-12-22 17:23:49.347031915 +0100
|
|
166 |
@@ -92,14 +92,14 @@
|
|
167 |
|
|
168 |
=over 4
|
|
169 |
|
|
170 |
-=item 0
|
|
171 |
+=item C<0>
|
|
172 |
|
|
173 |
The shutdown is not yet finished. Call SSL_shutdown() for a second time,
|
|
174 |
if a bidirectional shutdown shall be performed.
|
|
175 |
The output of L<SSL_get_error(3)|SSL_get_error(3)> may be misleading, as an
|
|
176 |
erroneous SSL_ERROR_SYSCALL may be flagged even though no error occurred.
|
155 | 177 |
|
156 | 178 |
-=item 1
|
157 | 179 |
+=item C<1>
|
158 | 180 |
|
159 | 181 |
The shutdown was successfully completed. The "close notify" alert was sent
|
160 | 182 |
and the peer's "close notify" alert was received.
|
161 | |
@@ -101,7 +101,7 @@ and the peer's "close notify" alert was
|
162 | |
|
163 | |
=over 4
|
164 | |
|
165 | |
-=item 0
|
166 | |
+=item C<0>
|
167 | |
|
168 | |
The shutdown is not yet finished. Call SSL_shutdown() for a second time,
|
169 | |
if a bidirectional shutdown shall be performed.
|
170 | |
--- openssl-1.0.1e.orig/doc/ssl/SSL_CTX_set_client_CA_list.pod
|
171 | |
+++ openssl-1.0.1e/doc/ssl/SSL_CTX_set_client_CA_list.pod
|
172 | |
@@ -66,7 +66,7 @@ values:
|
173 | |
|
174 | |
=over 4
|
175 | |
|
176 | |
-=item 1
|
177 | |
+=item C<1>
|
178 | |
|
179 | |
The operation succeeded.
|
180 | |
|
181 | |
@@ -74,7 +74,7 @@ The operation succeeded.
|
|
183 |
Index: openssl-1.0.1e/doc/ssl/SSL_CTX_set_client_CA_list.pod
|
|
184 |
===================================================================
|
|
185 |
--- openssl-1.0.1e.orig/doc/ssl/SSL_CTX_set_client_CA_list.pod 2013-12-22 17:21:52.913435572 +0100
|
|
186 |
+++ openssl-1.0.1e/doc/ssl/SSL_CTX_set_client_CA_list.pod 2013-12-22 17:24:41.985942861 +0100
|
|
187 |
@@ -66,13 +66,13 @@
|
182 | 188 |
|
183 | 189 |
=over 4
|
184 | 190 |
|
|
187 | 193 |
|
188 | 194 |
A failure while manipulating the STACK_OF(X509_NAME) object occurred or
|
189 | 195 |
the X509_NAME could not be extracted from B<cacert>. Check the error stack
|
190 | |
--- openssl-1.0.1e.orig/doc/ssl/SSL_accept.pod
|
191 | |
+++ openssl-1.0.1e/doc/ssl/SSL_accept.pod
|
192 | |
@@ -44,7 +44,7 @@ The following return values can occur:
|
193 | |
|
194 | |
=over 4
|
|
196 |
to find out the reason.
|
|
197 |
|
|
198 |
-=item 1
|
|
199 |
+=item C<1>
|
|
200 |
|
|
201 |
The operation succeeded.
|
|
202 |
|
|
203 |
Index: openssl-1.0.1e/doc/ssl/SSL_accept.pod
|
|
204 |
===================================================================
|
|
205 |
--- openssl-1.0.1e.orig/doc/ssl/SSL_accept.pod 2013-12-22 17:21:52.913435572 +0100
|
|
206 |
+++ openssl-1.0.1e/doc/ssl/SSL_accept.pod 2013-12-22 17:24:17.466450402 +0100
|
|
207 |
@@ -44,13 +44,13 @@
|
|
208 |
|
|
209 |
=over 4
|
|
210 |
|
|
211 |
-=item 0
|
|
212 |
+=item C<0>
|
|
213 |
|
|
214 |
The TLS/SSL handshake was not successful but was shut down controlled and
|
|
215 |
by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the
|
|
216 |
return value B<ret> to find out the reason.
|
195 | 217 |
|
196 | 218 |
-=item 1
|
197 | 219 |
+=item C<1>
|
198 | 220 |
|
199 | 221 |
The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
|
200 | 222 |
established.
|
201 | |
@@ -53,7 +53,7 @@ established.
|
202 | |
|
203 | |
=over 4
|
204 | |
|
205 | |
-=item 0
|
206 | |
+=item C<0>
|
207 | |
|
208 | |
The TLS/SSL handshake was not successful but was shut down controlled and
|
209 | |
by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the
|
210 | |
--- openssl-1.0.1e.orig/doc/ssl/SSL_CTX_set_session_id_context.pod
|
211 | |
+++ openssl-1.0.1e/doc/ssl/SSL_CTX_set_session_id_context.pod
|
212 | |
@@ -64,13 +64,13 @@ return the following values:
|
|
223 |
Index: openssl-1.0.1e/doc/ssl/SSL_CTX_set_session_id_context.pod
|
|
224 |
===================================================================
|
|
225 |
--- openssl-1.0.1e.orig/doc/ssl/SSL_CTX_set_session_id_context.pod 2013-12-22 17:21:52.913435572 +0100
|
|
226 |
+++ openssl-1.0.1e/doc/ssl/SSL_CTX_set_session_id_context.pod 2013-12-22 17:21:52.909435656 +0100
|
|
227 |
@@ -64,13 +64,13 @@
|
213 | 228 |
|
214 | 229 |
=over 4
|
215 | 230 |
|
|
225 | 240 |
|
226 | 241 |
The operation succeeded.
|
227 | 242 |
|
228 | |
--- openssl-1.0.1e.orig/doc/ssl/SSL_write.pod
|
229 | |
+++ openssl-1.0.1e/doc/ssl/SSL_write.pod
|
230 | |
@@ -79,7 +79,7 @@ The following return values can occur:
|
|
243 |
Index: openssl-1.0.1e/doc/ssl/SSL_write.pod
|
|
244 |
===================================================================
|
|
245 |
--- openssl-1.0.1e.orig/doc/ssl/SSL_write.pod 2013-12-22 17:21:52.913435572 +0100
|
|
246 |
+++ openssl-1.0.1e/doc/ssl/SSL_write.pod 2013-12-22 17:21:52.909435656 +0100
|
|
247 |
@@ -79,7 +79,7 @@
|
231 | 248 |
The write operation was successful, the return value is the number of
|
232 | 249 |
bytes actually written to the TLS/SSL connection.
|
233 | 250 |
|
|
236 | 253 |
|
237 | 254 |
The write operation was not successful. Probably the underlying connection
|
238 | 255 |
was closed. Call SSL_get_error() with the return value B<ret> to find out,
|
239 | |
--- openssl-1.0.1e.orig/doc/ssl/SSL_CTX_load_verify_locations.pod
|
240 | |
+++ openssl-1.0.1e/doc/ssl/SSL_CTX_load_verify_locations.pod
|
241 | |
@@ -100,13 +100,13 @@ The following return values can occur:
|
|
256 |
Index: openssl-1.0.1e/doc/ssl/SSL_CTX_load_verify_locations.pod
|
|
257 |
===================================================================
|
|
258 |
--- openssl-1.0.1e.orig/doc/ssl/SSL_CTX_load_verify_locations.pod 2013-12-22 17:21:52.913435572 +0100
|
|
259 |
+++ openssl-1.0.1e/doc/ssl/SSL_CTX_load_verify_locations.pod 2013-12-22 17:21:52.909435656 +0100
|
|
260 |
@@ -100,13 +100,13 @@
|
242 | 261 |
|
243 | 262 |
=over 4
|
244 | 263 |
|
|
254 | 273 |
|
255 | 274 |
The operation succeeded.
|
256 | 275 |
|
257 | |
--- openssl-1.0.1e.orig/doc/ssl/SSL_set_fd.pod
|
258 | |
+++ openssl-1.0.1e/doc/ssl/SSL_set_fd.pod
|
259 | |
@@ -35,11 +35,11 @@ The following return values can occur:
|
|
276 |
Index: openssl-1.0.1e/doc/ssl/SSL_set_fd.pod
|
|
277 |
===================================================================
|
|
278 |
--- openssl-1.0.1e.orig/doc/ssl/SSL_set_fd.pod 2013-12-22 17:21:52.913435572 +0100
|
|
279 |
+++ openssl-1.0.1e/doc/ssl/SSL_set_fd.pod 2013-12-22 17:21:52.909435656 +0100
|
|
280 |
@@ -35,11 +35,11 @@
|
260 | 281 |
|
261 | 282 |
=over 4
|
262 | 283 |
|
|
270 | 291 |
|
271 | 292 |
The operation succeeded.
|
272 | 293 |
|
273 | |
--- openssl-1.0.1e.orig/doc/ssl/SSL_CTX_use_psk_identity_hint.pod
|
274 | |
+++ openssl-1.0.1e/doc/ssl/SSL_CTX_use_psk_identity_hint.pod
|
275 | |
@@ -100,7 +100,7 @@ completely.
|
276 | |
|
277 | |
=over 4
|
|
294 |
Index: openssl-1.0.1e/doc/ssl/SSL_CTX_use_psk_identity_hint.pod
|
|
295 |
===================================================================
|
|
296 |
--- openssl-1.0.1e.orig/doc/ssl/SSL_CTX_use_psk_identity_hint.pod 2013-12-22 17:21:52.913435572 +0100
|
|
297 |
+++ openssl-1.0.1e/doc/ssl/SSL_CTX_use_psk_identity_hint.pod 2013-12-22 17:21:52.909435656 +0100
|
|
298 |
@@ -96,7 +96,7 @@
|
|
299 |
connection will fail with decryption_error before it will be finished
|
|
300 |
completely.
|
278 | 301 |
|
279 | 302 |
-=item 0
|
280 | 303 |
+=item C<0>
|
281 | 304 |
|
282 | 305 |
PSK identity was not found. An "unknown_psk_identity" alert message
|
283 | 306 |
will be sent and the connection setup fails.
|
284 | |
--- openssl-1.0.1e.orig/doc/ssl/SSL_read.pod
|
285 | |
+++ openssl-1.0.1e/doc/ssl/SSL_read.pod
|
286 | |
@@ -86,7 +86,7 @@ The following return values can occur:
|
|
307 |
Index: openssl-1.0.1e/doc/ssl/SSL_read.pod
|
|
308 |
===================================================================
|
|
309 |
--- openssl-1.0.1e.orig/doc/ssl/SSL_read.pod 2013-12-22 17:21:52.913435572 +0100
|
|
310 |
+++ openssl-1.0.1e/doc/ssl/SSL_read.pod 2013-12-22 17:21:52.909435656 +0100
|
|
311 |
@@ -86,7 +86,7 @@
|
287 | 312 |
The read operation was successful; the return value is the number of
|
288 | 313 |
bytes actually read from the TLS/SSL connection.
|
289 | 314 |
|
|
292 | 317 |
|
293 | 318 |
The read operation was not successful. The reason may either be a clean
|
294 | 319 |
shutdown due to a "close notify" alert sent by the peer (in which case
|
295 | |
--- openssl-1.0.1e.orig/doc/ssl/SSL_set_shutdown.pod
|
296 | |
+++ openssl-1.0.1e/doc/ssl/SSL_set_shutdown.pod
|
297 | |
@@ -24,7 +24,7 @@ The shutdown state of an ssl connection
|
|
320 |
Index: openssl-1.0.1e/doc/ssl/SSL_set_shutdown.pod
|
|
321 |
===================================================================
|
|
322 |
--- openssl-1.0.1e.orig/doc/ssl/SSL_set_shutdown.pod 2013-12-22 17:21:52.913435572 +0100
|
|
323 |
+++ openssl-1.0.1e/doc/ssl/SSL_set_shutdown.pod 2013-12-22 17:21:52.909435656 +0100
|
|
324 |
@@ -24,7 +24,7 @@
|
298 | 325 |
|
299 | 326 |
=over 4
|
300 | 327 |
|
|
303 | 330 |
|
304 | 331 |
No shutdown setting, yet.
|
305 | 332 |
|
306 | |
--- openssl-1.0.1e.orig/doc/ssl/SSL_CTX_add_session.pod
|
307 | |
+++ openssl-1.0.1e/doc/ssl/SSL_CTX_add_session.pod
|
308 | |
@@ -52,13 +52,13 @@ The following values are returned by all
|
|
333 |
Index: openssl-1.0.1e/doc/ssl/SSL_CTX_add_session.pod
|
|
334 |
===================================================================
|
|
335 |
--- openssl-1.0.1e.orig/doc/ssl/SSL_CTX_add_session.pod 2013-12-22 17:21:52.913435572 +0100
|
|
336 |
+++ openssl-1.0.1e/doc/ssl/SSL_CTX_add_session.pod 2013-12-22 17:21:52.909435656 +0100
|
|
337 |
@@ -52,13 +52,13 @@
|
309 | 338 |
|
310 | 339 |
=over 4
|
311 | 340 |
|
|
321 | 350 |
|
322 | 351 |
The operation succeeded.
|
323 | 352 |
|
324 | |
--- openssl-1.0.1e.orig/doc/ssl/SSL_do_handshake.pod
|
325 | |
+++ openssl-1.0.1e/doc/ssl/SSL_do_handshake.pod
|
326 | |
@@ -45,7 +45,7 @@ The following return values can occur:
|
327 | |
|
328 | |
=over 4
|
|
353 |
Index: openssl-1.0.1e/doc/ssl/SSL_do_handshake.pod
|
|
354 |
===================================================================
|
|
355 |
--- openssl-1.0.1e.orig/doc/ssl/SSL_do_handshake.pod 2013-12-22 17:21:52.913435572 +0100
|
|
356 |
+++ openssl-1.0.1e/doc/ssl/SSL_do_handshake.pod 2013-12-22 17:23:09.503854843 +0100
|
|
357 |
@@ -45,13 +45,13 @@
|
|
358 |
|
|
359 |
=over 4
|
|
360 |
|
|
361 |
-=item 0
|
|
362 |
+=item C<0>
|
|
363 |
|
|
364 |
The TLS/SSL handshake was not successful but was shut down controlled and
|
|
365 |
by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the
|
|
366 |
return value B<ret> to find out the reason.
|
329 | 367 |
|
330 | 368 |
-=item 1
|
331 | 369 |
+=item C<1>
|
332 | 370 |
|
333 | 371 |
The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
|
334 | 372 |
established.
|
335 | |
@@ -54,7 +54,7 @@ established.
|
336 | |
|
337 | |
=over 4
|
338 | |
|
339 | |
-=item 0
|
340 | |
+=item C<0>
|
341 | |
|
342 | |
The TLS/SSL handshake was not successful but was shut down controlled and
|
343 | |
by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the
|
344 | |
--- openssl-1.0.1e.orig/doc/ssl/SSL_COMP_add_compression_method.pod
|
345 | |
+++ openssl-1.0.1e/doc/ssl/SSL_COMP_add_compression_method.pod
|
346 | |
@@ -53,11 +53,11 @@ SSL_COMP_add_compression_method() may re
|
|
373 |
Index: openssl-1.0.1e/doc/ssl/SSL_COMP_add_compression_method.pod
|
|
374 |
===================================================================
|
|
375 |
--- openssl-1.0.1e.orig/doc/ssl/SSL_COMP_add_compression_method.pod 2013-12-22 17:21:52.913435572 +0100
|
|
376 |
+++ openssl-1.0.1e/doc/ssl/SSL_COMP_add_compression_method.pod 2013-12-22 17:21:52.909435656 +0100
|
|
377 |
@@ -53,11 +53,11 @@
|
347 | 378 |
|
348 | 379 |
=over 4
|
349 | 380 |
|
|
357 | 388 |
|
358 | 389 |
The operation failed. Check the error queue to find out the reason.
|
359 | 390 |
|
360 | |
--- openssl-1.0.1e.orig/doc/ssl/SSL_CTX_set_ssl_version.pod
|
361 | |
+++ openssl-1.0.1e/doc/ssl/SSL_CTX_set_ssl_version.pod
|
362 | |
@@ -42,11 +42,11 @@ and SSL_set_ssl_method():
|
|
391 |
Index: openssl-1.0.1e/doc/ssl/SSL_CTX_set_ssl_version.pod
|
|
392 |
===================================================================
|
|
393 |
--- openssl-1.0.1e.orig/doc/ssl/SSL_CTX_set_ssl_version.pod 2013-12-22 17:21:52.913435572 +0100
|
|
394 |
+++ openssl-1.0.1e/doc/ssl/SSL_CTX_set_ssl_version.pod 2013-12-22 17:21:52.909435656 +0100
|
|
395 |
@@ -42,11 +42,11 @@
|
363 | 396 |
|
364 | 397 |
=over 4
|
365 | 398 |
|