summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/crypto (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Just like every web browser expands until it can read mail, every modularmiod2014-04-151-3/+3
| | | | | | | | | | | | | | | library expands until it has its own dlfcn wrapper, and libcrypto is no exception. Remove the non-dlfcn DSO methods. This causes public DSO_METHOD_{beos,dl,vms,win32} to disappear (major bump coming soon). Note that portable software ought to use DSO_METHOD_openssl instead of picking the backend directly (which makes one wonder why the backends are exposed, as it is unlikely that more than one can work on your system). ok beck@ deraadt@
* remove FIPS mode support. people who require FIPS can buy something thattedu2014-04-151-3/+3
| | | | | meets their needs, but dumping it in here only penalizes the rest of us. ok beck deraadt
* Send the rotIBM stream cipher (ebcdic) to Valhalla to party for eternitybeck2014-04-151-3/+2
| | | | | with the bearded ones... some API's that nobody should be using will dissapear with this commit.
* As we now remove it permanently, we no longer need NO_WINDOWS_BRAINDEATHbeck2014-04-151-2/+2
| | | | | as a build time option... ok deraadt@ miod@
* Replace the old OpenSSL PRNG by direct use of arc4random_buf(), keeping themiod2014-04-151-2/+2
| | | | | | | | | | | | | | | | | | | | | existing RAND interfaces unchanged. All interfaces allowing external feed or seed of the RNG (either from a file or a local entropy gathering daemon) are kept for ABI compatibility, but are no longer do anything. While the OpenSSL PRNG was required 15+ years ago when many systems lacked proper entropy collection, things have evolved and one can reasonably assume it is better to use the kernel (system global) entropy pool rather than trying to build one's own and having to compensate for thread scheduling... <RANT> Whoever thought that RAND_screen(), feeding the PRNG with the contents of the local workstation's display, under Win32, was a smart idea, ought to be banned from security programming. </RANT> ok beck@ deraadt@ tedu@
* revert 1.2 and define OPENSSL_NO_EC_NISTP_64_GCC_128 again, it has a downsidesthen2014-04-141-0/+3
| | | | (breaks ssh ecdsa keys)
* Don't bother compiling files which end up containingmiod2014-04-141-2/+2
| | | | | | #if OPENSSL_SYS_NOTYOURS <whole file> #endif
* Cope with the removal of openssl/symhacks.hderaadt2014-04-131-2/+1
|
* Don't edit on cvs. 23.1 as intended.miod2014-04-131-2/+2
|
* Do not install e_os.h, it is not an external header and should not be usedmiod2014-04-131-2/+1
| | | | by anything in userland.
* Move undocumented internal OPENSSL_DIR interface from libcrypto to libssl,miod2014-04-131-2/+2
| | | | | | so that libssl no longer need to access the non-external headers of libcrypto to build. No library bump, riding upon the recent update.
* Crank libcrypto minor (addition of BN_consttime_swap and CRYPTO_memcmp)miod2014-04-131-1/+1
| | | | and libssl major (ssl_check_clienthello_tlsext split into two functions)
* No longer define OPENSSL_NO_EC_NISTP_64_GCC_128 on amd64; requested by djmmiod2014-04-131-3/+0
|
* Move build machinery for libcrypto from libssl/crypto to libcrypto, as wellmiod2014-04-1116-0/+4553
as configuration files; split manpages and .pc files between libcrypto and libssl. No functional change, only there to make engineering easier, and libcrypto sources are still found in libssl/src/crypto at the moment. ok reyk@, also discussed with deraadt@ beck@ and the usual crypto suspects.