If available rdrand is used as an additional entropy source for the
PRNG and for additional input in FIPS mode.

(and shave off cycle even from integer-only code)

(and update performance data, and fix typo)

but keep it disabled, too little gain... Add some Atom-specific
optimization.

PR: 3202

If content is detached and not binary mode translate the input to
CRLF format. Before this change the input was verified verbatim
which lead to a discrepancy between sign and verify.

(cherry picked from commit a6c62f0c25a756c263a80ce52afbae888028e986)

(and ensure stack alignment in the process)

It worked because it was never called.

SHA512_Transform was initially added rather as tribute to tradition
than for practucal reasons. But use was recently found in ssl/s3_cbc.c
and it turned to be problematic on platforms that don't tolerate
misasligned references to memory and lack assembly subroutine.

Move the IP, email and host checking fields from the public
X509_VERIFY_PARAM structure into an opaque X509_VERIFY_PARAM_ID
structure. By doing this the structure can be modified in future
without risk of breaking any applications.
(cherry picked from commit adc6bd73e3bd10ce6e76867482e8d137071298d7)

Conflicts:

	crypto/x509/x509_vpm.c

For consistency with other cases if we are performing
partial chain verification with just one certificate
notify the callback with ok==1.
(cherry picked from commit 852553d9005e13aed7feb986a5d71cb885b994c7)

(cherry picked from commit 16898401bd47a153fbf799127ff57fdcfcbd324f)

This also eliminates code duplication between x86_64-mont and x86_64-mont
and optimizes even original non-MULX code.

Suggested by: Marcello Cerri

Suggested by: Marcello Cerri

PR: 3189
Submitted by: Oscar Ciurana

rsaz_exp.c: harmonize line terminating;
asm/rsaz-*.pl: minor optimizations.

(cherry picked from commit 1abfa78a8ba714f7e47bd674db53dbe303cd1ce7)

Some functions such as EVP_VerifyFinal only finalise a copy of the passed
context in case an application wants to digest more data. Doing this when
it is not needed is inefficient and many applications don't require it.

For compatibility the default is to still finalise a copy unless the
flag EVP_MD_CTX_FLAG_FINALISE is set in which case the passed
context is finalised an *no* further data can be digested after
finalisation.

PR: 3165
Submitted by: Daniel Richard G.

PR: 3165