src/lib/libmd, branch release/10.1.0

MFC r263863:

2014-03-31T00:28:54Z

Dereference nonexistent md2(3) manual. Sponsored by: The FreeBSD Foundation

Remove the RFC 1319 MD2 Message-Digest Algorithm routines from libmd.

2012-04-28T02:48:51Z

1. The licensing terms for the MD2 routines from RFC is not under a BSD-like license. Instead it is only granted for non-commercial Internet Privacy-Enhanced Mail. 2. MD2 is quite deprecated as it is no longer considered a cryptographically strong algorithm. Discussed with: so (cperciva), core

Rewrite HISTORY: The SHA256 code first appeared in 6.0, and the SHA512

2011-06-27T02:10:10Z

code in 9.0; neither existed in FreeBSD 4.0.

Add SHA512 (Actually, this is Colin Percival's code for SHA256, with

2011-04-09T13:56:29Z

relevant constants changed). While I'm here clean up the tests and Makefile. PR: misc/124164 Submitted by: KIMURA Yasuhiro < yasu utahime org > MFC after: 1 month

Fix some leftover binaries and shared libraries in the system that still

2011-02-15T22:03:09Z

have an executable stack, due to linking in hand-assembled .S or .s files, that have no .GNU-stack sections: RWX --- --- /lib/libcrypto.so.6 RWX --- --- /lib/libmd.so.5 RWX --- --- /lib/libz.so.6 RWX --- --- /lib/libzpool.so.2 RWX --- --- /usr/lib/liblzma.so.5 These were found using scanelf, from the sysutils/pax-utils port. Reviewed by: kib

Build lib/ with WARNS=6 by default.

2010-01-02T09:58:07Z

Similar to libexec/, do the same with lib/. Make WARNS=6 the norm and lower it when needed. I'm setting WARNS?=0 for secure/. It seems secure/ includes the Makefile.inc provided by lib/. I'm not going to touch that directory. Most of the code there is contributed anyway.

Remove reference to no longer existing document.

2009-01-09T11:45:13Z

Spotted by: Bjoern Voigt

Make the "test" target test the compiled version, instead of the

2008-12-02T19:49:41Z

installed version of the md library.

Use unsigned comparisons. Prior to this commit, SHA1_Update and

2007-05-14T05:00:37Z

RIPEMD160_Update were broken when all of the following conditions applied: (1) The platform is i386. (2) The program calling *_Update is statically linked to libmd. (3) The buffer provided to *_Update is aligned modulo 4 bytes. (4) The buffer extends beyond 2GB. Due to the design of this code, SHA1_Update and RIPEMD160_Update will still be broken if conditions (1)-(3) apply AND the buffer extends beyond 4GB (i.e., there is an integer overflow in computing "data + len"). Since this remaining bug simply replaces SIGSEGV with a bogus hash (and non-broken programs should never provide such operands) I don't consider it to be a serious problem. MFC After: 1 week PR: kern/102795

Fix an 11 year old mistake: Let the hash functions take a void* instead

2006-01-17T15:35:57Z

of unsigned char* argument.