Annotation of /trunk/openssl/patches/openssl-1.0.1f-perl-5.18.patch
Parent Directory | Revision Log
Revision 2380 -
(hide annotations)
(download)
Mon Jan 27 14:41:27 2014 UTC (10 years, 8 months ago) by niro
File size: 7820 byte(s)
Mon Jan 27 14:41:27 2014 UTC (10 years, 8 months ago) by niro
File size: 7820 byte(s)
-fixed build with perl-5.18
1 | niro | 2380 | Forward-ported from openssl-1.0.1e-perl-5.18.patch |
2 | Fixes install with perl-5.18. | ||
3 | |||
4 | https://bugs.gentoo.org/show_bug.cgi?id=497286 | ||
5 | |||
6 | Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> | ||
7 | |||
8 | --- openssl-1.0.1f/doc/apps/cms.pod | ||
9 | +++ openssl-1.0.1f/doc/apps/cms.pod | ||
10 | @@ -450,28 +450,28 @@ | ||
11 | |||
12 | =over 4 | ||
13 | |||
14 | -=item 0 | ||
15 | +=item C<0> | ||
16 | |||
17 | the operation was completely successfully. | ||
18 | |||
19 | -=item 1 | ||
20 | +=item C<1> | ||
21 | |||
22 | an error occurred parsing the command options. | ||
23 | |||
24 | -=item 2 | ||
25 | +=item C<2> | ||
26 | |||
27 | one of the input files could not be read. | ||
28 | |||
29 | -=item 3 | ||
30 | +=item C<3> | ||
31 | |||
32 | an error occurred creating the CMS file or when reading the MIME | ||
33 | message. | ||
34 | |||
35 | -=item 4 | ||
36 | +=item C<4> | ||
37 | |||
38 | an error occurred decrypting or verifying the message. | ||
39 | |||
40 | -=item 5 | ||
41 | +=item C<5> | ||
42 | |||
43 | the message was verified correctly but an error occurred writing out | ||
44 | the signers certificates. | ||
45 | --- openssl-1.0.1f/doc/apps/smime.pod | ||
46 | +++ openssl-1.0.1f/doc/apps/smime.pod | ||
47 | @@ -308,28 +308,28 @@ | ||
48 | |||
49 | =over 4 | ||
50 | |||
51 | -=item 0 | ||
52 | +=item C<0> | ||
53 | |||
54 | the operation was completely successfully. | ||
55 | |||
56 | -=item 1 | ||
57 | +=item C<1> | ||
58 | |||
59 | an error occurred parsing the command options. | ||
60 | |||
61 | -=item 2 | ||
62 | +=item C<2> | ||
63 | |||
64 | one of the input files could not be read. | ||
65 | |||
66 | -=item 3 | ||
67 | +=item C<3> | ||
68 | |||
69 | an error occurred creating the PKCS#7 file or when reading the MIME | ||
70 | message. | ||
71 | |||
72 | -=item 4 | ||
73 | +=item C<4> | ||
74 | |||
75 | an error occurred decrypting or verifying the message. | ||
76 | |||
77 | -=item 5 | ||
78 | +=item C<5> | ||
79 | |||
80 | the message was verified correctly but an error occurred writing out | ||
81 | the signers certificates. | ||
82 | --- openssl-1.0.1f/doc/ssl/SSL_accept.pod | ||
83 | +++ openssl-1.0.1f/doc/ssl/SSL_accept.pod | ||
84 | @@ -44,13 +44,13 @@ | ||
85 | |||
86 | =over 4 | ||
87 | |||
88 | -=item 0 | ||
89 | +=item C<0> | ||
90 | |||
91 | The TLS/SSL handshake was not successful but was shut down controlled and | ||
92 | by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the | ||
93 | return value B<ret> to find out the reason. | ||
94 | |||
95 | -=item 1 | ||
96 | +=item C<1> | ||
97 | |||
98 | The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been | ||
99 | established. | ||
100 | --- openssl-1.0.1f/doc/ssl/SSL_clear.pod | ||
101 | +++ openssl-1.0.1f/doc/ssl/SSL_clear.pod | ||
102 | @@ -56,12 +56,12 @@ | ||
103 | |||
104 | =over 4 | ||
105 | |||
106 | -=item 0 | ||
107 | +=item C<0> | ||
108 | |||
109 | The SSL_clear() operation could not be performed. Check the error stack to | ||
110 | find out the reason. | ||
111 | |||
112 | -=item 1 | ||
113 | +=item C<1> | ||
114 | |||
115 | The SSL_clear() operation was successful. | ||
116 | |||
117 | --- openssl-1.0.1f/doc/ssl/SSL_COMP_add_compression_method.pod | ||
118 | +++ openssl-1.0.1f/doc/ssl/SSL_COMP_add_compression_method.pod | ||
119 | @@ -53,11 +53,11 @@ | ||
120 | |||
121 | =over 4 | ||
122 | |||
123 | -=item 0 | ||
124 | +=item C<0> | ||
125 | |||
126 | The operation succeeded. | ||
127 | |||
128 | -=item 1 | ||
129 | +=item C<1> | ||
130 | |||
131 | The operation failed. Check the error queue to find out the reason. | ||
132 | |||
133 | --- openssl-1.0.1f/doc/ssl/SSL_connect.pod | ||
134 | +++ openssl-1.0.1f/doc/ssl/SSL_connect.pod | ||
135 | @@ -41,13 +41,13 @@ | ||
136 | |||
137 | =over 4 | ||
138 | |||
139 | -=item 0 | ||
140 | +=item C<0> | ||
141 | |||
142 | The TLS/SSL handshake was not successful but was shut down controlled and | ||
143 | by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the | ||
144 | return value B<ret> to find out the reason. | ||
145 | |||
146 | -=item 1 | ||
147 | +=item C<1> | ||
148 | |||
149 | The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been | ||
150 | established. | ||
151 | --- openssl-1.0.1f/doc/ssl/SSL_CTX_add_session.pod | ||
152 | +++ openssl-1.0.1f/doc/ssl/SSL_CTX_add_session.pod | ||
153 | @@ -52,13 +52,13 @@ | ||
154 | |||
155 | =over 4 | ||
156 | |||
157 | -=item 0 | ||
158 | +=item C<0> | ||
159 | |||
160 | The operation failed. In case of the add operation, it was tried to add | ||
161 | the same (identical) session twice. In case of the remove operation, the | ||
162 | session was not found in the cache. | ||
163 | |||
164 | -=item 1 | ||
165 | +=item C<1> | ||
166 | |||
167 | The operation succeeded. | ||
168 | |||
169 | --- openssl-1.0.1f/doc/ssl/SSL_CTX_load_verify_locations.pod | ||
170 | +++ openssl-1.0.1f/doc/ssl/SSL_CTX_load_verify_locations.pod | ||
171 | @@ -100,13 +100,13 @@ | ||
172 | |||
173 | =over 4 | ||
174 | |||
175 | -=item 0 | ||
176 | +=item C<0> | ||
177 | |||
178 | The operation failed because B<CAfile> and B<CApath> are NULL or the | ||
179 | processing at one of the locations specified failed. Check the error | ||
180 | stack to find out the reason. | ||
181 | |||
182 | -=item 1 | ||
183 | +=item C<1> | ||
184 | |||
185 | The operation succeeded. | ||
186 | |||
187 | --- openssl-1.0.1f/doc/ssl/SSL_CTX_set_client_CA_list.pod | ||
188 | +++ openssl-1.0.1f/doc/ssl/SSL_CTX_set_client_CA_list.pod | ||
189 | @@ -66,13 +66,13 @@ | ||
190 | |||
191 | =over 4 | ||
192 | |||
193 | -=item 0 | ||
194 | +=item C<0> | ||
195 | |||
196 | A failure while manipulating the STACK_OF(X509_NAME) object occurred or | ||
197 | the X509_NAME could not be extracted from B<cacert>. Check the error stack | ||
198 | to find out the reason. | ||
199 | |||
200 | -=item 1 | ||
201 | +=item C<1> | ||
202 | |||
203 | The operation succeeded. | ||
204 | |||
205 | --- openssl-1.0.1f/doc/ssl/SSL_CTX_set_session_id_context.pod | ||
206 | +++ openssl-1.0.1f/doc/ssl/SSL_CTX_set_session_id_context.pod | ||
207 | @@ -64,13 +64,13 @@ | ||
208 | |||
209 | =over 4 | ||
210 | |||
211 | -=item 0 | ||
212 | +=item C<0> | ||
213 | |||
214 | The length B<sid_ctx_len> of the session id context B<sid_ctx> exceeded | ||
215 | the maximum allowed length of B<SSL_MAX_SSL_SESSION_ID_LENGTH>. The error | ||
216 | is logged to the error stack. | ||
217 | |||
218 | -=item 1 | ||
219 | +=item C<1> | ||
220 | |||
221 | The operation succeeded. | ||
222 | |||
223 | --- openssl-1.0.1f/doc/ssl/SSL_CTX_set_ssl_version.pod | ||
224 | +++ openssl-1.0.1f/doc/ssl/SSL_CTX_set_ssl_version.pod | ||
225 | @@ -42,11 +42,11 @@ | ||
226 | |||
227 | =over 4 | ||
228 | |||
229 | -=item 0 | ||
230 | +=item C<0> | ||
231 | |||
232 | The new choice failed, check the error stack to find out the reason. | ||
233 | |||
234 | -=item 1 | ||
235 | +=item C<1> | ||
236 | |||
237 | The operation succeeded. | ||
238 | |||
239 | --- openssl-1.0.1f/doc/ssl/SSL_CTX_use_psk_identity_hint.pod | ||
240 | +++ openssl-1.0.1f/doc/ssl/SSL_CTX_use_psk_identity_hint.pod | ||
241 | @@ -96,7 +96,7 @@ | ||
242 | connection will fail with decryption_error before it will be finished | ||
243 | completely. | ||
244 | |||
245 | -=item 0 | ||
246 | +=item C<0> | ||
247 | |||
248 | PSK identity was not found. An "unknown_psk_identity" alert message | ||
249 | will be sent and the connection setup fails. | ||
250 | --- openssl-1.0.1f/doc/ssl/SSL_do_handshake.pod | ||
251 | +++ openssl-1.0.1f/doc/ssl/SSL_do_handshake.pod | ||
252 | @@ -45,13 +45,13 @@ | ||
253 | |||
254 | =over 4 | ||
255 | |||
256 | -=item 0 | ||
257 | +=item C<0> | ||
258 | |||
259 | The TLS/SSL handshake was not successful but was shut down controlled and | ||
260 | by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the | ||
261 | return value B<ret> to find out the reason. | ||
262 | |||
263 | -=item 1 | ||
264 | +=item C<1> | ||
265 | |||
266 | The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been | ||
267 | established. | ||
268 | --- openssl-1.0.1f/doc/ssl/SSL_read.pod | ||
269 | +++ openssl-1.0.1f/doc/ssl/SSL_read.pod | ||
270 | @@ -86,7 +86,7 @@ | ||
271 | The read operation was successful; the return value is the number of | ||
272 | bytes actually read from the TLS/SSL connection. | ||
273 | |||
274 | -=item 0 | ||
275 | +=item C<0> | ||
276 | |||
277 | The read operation was not successful. The reason may either be a clean | ||
278 | shutdown due to a "close notify" alert sent by the peer (in which case | ||
279 | --- openssl-1.0.1f/doc/ssl/SSL_session_reused.pod | ||
280 | +++ openssl-1.0.1f/doc/ssl/SSL_session_reused.pod | ||
281 | @@ -27,11 +27,11 @@ | ||
282 | |||
283 | =over 4 | ||
284 | |||
285 | -=item 0 | ||
286 | +=item C<0> | ||
287 | |||
288 | A new session was negotiated. | ||
289 | |||
290 | -=item 1 | ||
291 | +=item C<1> | ||
292 | |||
293 | A session was reused. | ||
294 | |||
295 | --- openssl-1.0.1f/doc/ssl/SSL_set_fd.pod | ||
296 | +++ openssl-1.0.1f/doc/ssl/SSL_set_fd.pod | ||
297 | @@ -35,11 +35,11 @@ | ||
298 | |||
299 | =over 4 | ||
300 | |||
301 | -=item 0 | ||
302 | +=item C<0> | ||
303 | |||
304 | The operation failed. Check the error stack to find out why. | ||
305 | |||
306 | -=item 1 | ||
307 | +=item C<1> | ||
308 | |||
309 | The operation succeeded. | ||
310 | |||
311 | --- openssl-1.0.1f/doc/ssl/SSL_set_session.pod | ||
312 | +++ openssl-1.0.1f/doc/ssl/SSL_set_session.pod | ||
313 | @@ -37,11 +37,11 @@ | ||
314 | |||
315 | =over 4 | ||
316 | |||
317 | -=item 0 | ||
318 | +=item C<0> | ||
319 | |||
320 | The operation failed; check the error stack to find out the reason. | ||
321 | |||
322 | -=item 1 | ||
323 | +=item C<1> | ||
324 | |||
325 | The operation succeeded. | ||
326 | |||
327 | --- openssl-1.0.1f/doc/ssl/SSL_shutdown.pod | ||
328 | +++ openssl-1.0.1f/doc/ssl/SSL_shutdown.pod | ||
329 | @@ -92,14 +92,14 @@ | ||
330 | |||
331 | =over 4 | ||
332 | |||
333 | -=item 0 | ||
334 | +=item C<0> | ||
335 | |||
336 | The shutdown is not yet finished. Call SSL_shutdown() for a second time, | ||
337 | if a bidirectional shutdown shall be performed. | ||
338 | The output of L<SSL_get_error(3)|SSL_get_error(3)> may be misleading, as an | ||
339 | erroneous SSL_ERROR_SYSCALL may be flagged even though no error occurred. | ||
340 | |||
341 | -=item 1 | ||
342 | +=item C<1> | ||
343 | |||
344 | The shutdown was successfully completed. The "close notify" alert was sent | ||
345 | and the peer's "close notify" alert was received. | ||
346 | --- openssl-1.0.1f/doc/ssl/SSL_write.pod | ||
347 | +++ openssl-1.0.1f/doc/ssl/SSL_write.pod | ||
348 | @@ -79,7 +79,7 @@ | ||
349 | The write operation was successful, the return value is the number of | ||
350 | bytes actually written to the TLS/SSL connection. | ||
351 | |||
352 | -=item 0 | ||
353 | +=item C<0> | ||
354 | |||
355 | The write operation was not successful. Probably the underlying connection | ||
356 | was closed. Call SSL_get_error() with the return value B<ret> to find out, |