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
11 the operation was completely successfully.
16 an error occurred parsing the command options.
21 one of the input files could not be read.
26 an error occurred creating the CMS file or when reading the MIME
32 an error occurred decrypting or verifying the message.
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
49 the operation was completely successfully.
54 an error occurred parsing the command options.
59 one of the input files could not be read.
64 an error occurred creating the PKCS#7 file or when reading the MIME
70 an error occurred decrypting or verifying the message.
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
87 The TSA client computes a one-way hash value for a data file and sends
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.
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
113 A good hashing algorithm to mix things up and to convert the RNG 'state'
119 An initial source of random 'state'.
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).
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.
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.
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.
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.
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
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.
174 The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
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
186 The SSL_clear() operation could not be performed. Check the error stack to
192 The SSL_clear() operation was successful.
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
204 The operation succeeded.
209 The operation failed. Check the error queue to find out the reason.
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
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.
228 The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
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
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.
247 The operation succeeded.
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 @@
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.
266 The operation succeeded.
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
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.
285 The operation succeeded.
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
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.
304 The operation succeeded.
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
316 The new choice failed, check the error stack to find out the reason.
321 The operation succeeded.
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
327 connection will fail with decryption_error before it will be finished
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
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.
352 The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
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
358 The read operation was successful; the return value is the number of
359 bytes actually read from the TLS/SSL connection.
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
376 A new session was negotiated.
381 A session was reused.
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
393 The operation failed. Check the error stack to find out why.
398 The operation succeeded.
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
410 The operation failed; check the error stack to find out the reason.
415 The operation succeeded.
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
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.
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
441 The write operation was successful, the return value is the number of
442 bytes actually written to the TLS/SSL connection.
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,