xref: /onnv-gate/usr/src/common/openssl/crypto/md4/md4_locl.h (revision 2139:6243c3338933)
10Sstevel@tonic-gate /* crypto/md4/md4_locl.h */
20Sstevel@tonic-gate /* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
30Sstevel@tonic-gate  * All rights reserved.
40Sstevel@tonic-gate  *
50Sstevel@tonic-gate  * This package is an SSL implementation written
60Sstevel@tonic-gate  * by Eric Young (eay@cryptsoft.com).
70Sstevel@tonic-gate  * The implementation was written so as to conform with Netscapes SSL.
80Sstevel@tonic-gate  *
90Sstevel@tonic-gate  * This library is free for commercial and non-commercial use as long as
100Sstevel@tonic-gate  * the following conditions are aheared to.  The following conditions
110Sstevel@tonic-gate  * apply to all code found in this distribution, be it the RC4, RSA,
120Sstevel@tonic-gate  * lhash, DES, etc., code; not just the SSL code.  The SSL documentation
130Sstevel@tonic-gate  * included with this distribution is covered by the same copyright terms
140Sstevel@tonic-gate  * except that the holder is Tim Hudson (tjh@cryptsoft.com).
150Sstevel@tonic-gate  *
160Sstevel@tonic-gate  * Copyright remains Eric Young's, and as such any Copyright notices in
170Sstevel@tonic-gate  * the code are not to be removed.
180Sstevel@tonic-gate  * If this package is used in a product, Eric Young should be given attribution
190Sstevel@tonic-gate  * as the author of the parts of the library used.
200Sstevel@tonic-gate  * This can be in the form of a textual message at program startup or
210Sstevel@tonic-gate  * in documentation (online or textual) provided with the package.
220Sstevel@tonic-gate  *
230Sstevel@tonic-gate  * Redistribution and use in source and binary forms, with or without
240Sstevel@tonic-gate  * modification, are permitted provided that the following conditions
250Sstevel@tonic-gate  * are met:
260Sstevel@tonic-gate  * 1. Redistributions of source code must retain the copyright
270Sstevel@tonic-gate  *    notice, this list of conditions and the following disclaimer.
280Sstevel@tonic-gate  * 2. Redistributions in binary form must reproduce the above copyright
290Sstevel@tonic-gate  *    notice, this list of conditions and the following disclaimer in the
300Sstevel@tonic-gate  *    documentation and/or other materials provided with the distribution.
310Sstevel@tonic-gate  * 3. All advertising materials mentioning features or use of this software
320Sstevel@tonic-gate  *    must display the following acknowledgement:
330Sstevel@tonic-gate  *    "This product includes cryptographic software written by
340Sstevel@tonic-gate  *     Eric Young (eay@cryptsoft.com)"
350Sstevel@tonic-gate  *    The word 'cryptographic' can be left out if the rouines from the library
360Sstevel@tonic-gate  *    being used are not cryptographic related :-).
370Sstevel@tonic-gate  * 4. If you include any Windows specific code (or a derivative thereof) from
380Sstevel@tonic-gate  *    the apps directory (application code) you must include an acknowledgement:
390Sstevel@tonic-gate  *    "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
400Sstevel@tonic-gate  *
410Sstevel@tonic-gate  * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
420Sstevel@tonic-gate  * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
430Sstevel@tonic-gate  * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
440Sstevel@tonic-gate  * ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
450Sstevel@tonic-gate  * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
460Sstevel@tonic-gate  * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
470Sstevel@tonic-gate  * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
480Sstevel@tonic-gate  * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
490Sstevel@tonic-gate  * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
500Sstevel@tonic-gate  * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
510Sstevel@tonic-gate  * SUCH DAMAGE.
520Sstevel@tonic-gate  *
530Sstevel@tonic-gate  * The licence and distribution terms for any publically available version or
540Sstevel@tonic-gate  * derivative of this code cannot be changed.  i.e. this code cannot simply be
550Sstevel@tonic-gate  * copied and put under another distribution licence
560Sstevel@tonic-gate  * [including the GNU Public Licence.]
570Sstevel@tonic-gate  */
580Sstevel@tonic-gate 
590Sstevel@tonic-gate #include <stdlib.h>
600Sstevel@tonic-gate #include <string.h>
610Sstevel@tonic-gate #include <openssl/opensslconf.h>
620Sstevel@tonic-gate #include <openssl/md4.h>
630Sstevel@tonic-gate 
640Sstevel@tonic-gate #ifndef MD4_LONG_LOG2
650Sstevel@tonic-gate #define MD4_LONG_LOG2 2 /* default to 32 bits */
660Sstevel@tonic-gate #endif
670Sstevel@tonic-gate 
68*2139Sjp161948 void md4_block_host_order (MD4_CTX *c, const void *p,size_t num);
69*2139Sjp161948 void md4_block_data_order (MD4_CTX *c, const void *p,size_t num);
700Sstevel@tonic-gate 
710Sstevel@tonic-gate #if defined(__i386) || defined(__i386__) || defined(_M_IX86) || defined(__INTEL__)
72*2139Sjp161948 # if !defined(B_ENDIAN)
730Sstevel@tonic-gate /*
740Sstevel@tonic-gate  * *_block_host_order is expected to handle aligned data while
750Sstevel@tonic-gate  * *_block_data_order - unaligned. As algorithm and host (x86)
760Sstevel@tonic-gate  * are in this case of the same "endianness" these two are
770Sstevel@tonic-gate  * otherwise indistinguishable. But normally you don't want to
780Sstevel@tonic-gate  * call the same function because unaligned access in places
790Sstevel@tonic-gate  * where alignment is expected is usually a "Bad Thing". Indeed,
800Sstevel@tonic-gate  * on RISCs you get punished with BUS ERROR signal or *severe*
810Sstevel@tonic-gate  * performance degradation. Intel CPUs are in turn perfectly
820Sstevel@tonic-gate  * capable of loading unaligned data without such drastic side
830Sstevel@tonic-gate  * effect. Yes, they say it's slower than aligned load, but no
840Sstevel@tonic-gate  * exception is generated and therefore performance degradation
850Sstevel@tonic-gate  * is *incomparable* with RISCs. What we should weight here is
860Sstevel@tonic-gate  * costs of unaligned access against costs of aligning data.
870Sstevel@tonic-gate  * According to my measurements allowing unaligned access results
880Sstevel@tonic-gate  * in ~9% performance improvement on Pentium II operating at
890Sstevel@tonic-gate  * 266MHz. I won't be surprised if the difference will be higher
900Sstevel@tonic-gate  * on faster systems:-)
910Sstevel@tonic-gate  *
920Sstevel@tonic-gate  *				<appro@fy.chalmers.se>
930Sstevel@tonic-gate  */
94*2139Sjp161948 # define md4_block_data_order md4_block_host_order
95*2139Sjp161948 # endif
960Sstevel@tonic-gate #endif
970Sstevel@tonic-gate 
980Sstevel@tonic-gate #define DATA_ORDER_IS_LITTLE_ENDIAN
990Sstevel@tonic-gate 
1000Sstevel@tonic-gate #define HASH_LONG		MD4_LONG
1010Sstevel@tonic-gate #define HASH_LONG_LOG2		MD4_LONG_LOG2
1020Sstevel@tonic-gate #define HASH_CTX		MD4_CTX
1030Sstevel@tonic-gate #define HASH_CBLOCK		MD4_CBLOCK
1040Sstevel@tonic-gate #define HASH_LBLOCK		MD4_LBLOCK
1050Sstevel@tonic-gate #define HASH_UPDATE		MD4_Update
1060Sstevel@tonic-gate #define HASH_TRANSFORM		MD4_Transform
1070Sstevel@tonic-gate #define HASH_FINAL		MD4_Final
1080Sstevel@tonic-gate #define	HASH_MAKE_STRING(c,s)	do {	\
1090Sstevel@tonic-gate 	unsigned long ll;		\
1100Sstevel@tonic-gate 	ll=(c)->A; HOST_l2c(ll,(s));	\
1110Sstevel@tonic-gate 	ll=(c)->B; HOST_l2c(ll,(s));	\
1120Sstevel@tonic-gate 	ll=(c)->C; HOST_l2c(ll,(s));	\
1130Sstevel@tonic-gate 	ll=(c)->D; HOST_l2c(ll,(s));	\
1140Sstevel@tonic-gate 	} while (0)
1150Sstevel@tonic-gate #define HASH_BLOCK_HOST_ORDER	md4_block_host_order
1160Sstevel@tonic-gate #if !defined(L_ENDIAN) || defined(md4_block_data_order)
1170Sstevel@tonic-gate #define	HASH_BLOCK_DATA_ORDER	md4_block_data_order
1180Sstevel@tonic-gate /*
1190Sstevel@tonic-gate  * Little-endians (Intel and Alpha) feel better without this.
1200Sstevel@tonic-gate  * It looks like memcpy does better job than generic
1210Sstevel@tonic-gate  * md4_block_data_order on copying-n-aligning input data.
1220Sstevel@tonic-gate  * But frankly speaking I didn't expect such result on Alpha.
1230Sstevel@tonic-gate  * On the other hand I've got this with egcs-1.0.2 and if
1240Sstevel@tonic-gate  * program is compiled with another (better?) compiler it
1250Sstevel@tonic-gate  * might turn out other way around.
1260Sstevel@tonic-gate  *
1270Sstevel@tonic-gate  *				<appro@fy.chalmers.se>
1280Sstevel@tonic-gate  */
1290Sstevel@tonic-gate #endif
1300Sstevel@tonic-gate 
1310Sstevel@tonic-gate #include "md32_common.h"
1320Sstevel@tonic-gate 
1330Sstevel@tonic-gate /*
1340Sstevel@tonic-gate #define	F(x,y,z)	(((x) & (y))  |  ((~(x)) & (z)))
1350Sstevel@tonic-gate #define	G(x,y,z)	(((x) & (y))  |  ((x) & ((z))) | ((y) & ((z))))
1360Sstevel@tonic-gate */
1370Sstevel@tonic-gate 
1380Sstevel@tonic-gate /* As pointed out by Wei Dai <weidai@eskimo.com>, the above can be
1390Sstevel@tonic-gate  * simplified to the code below.  Wei attributes these optimizations
1400Sstevel@tonic-gate  * to Peter Gutmann's SHS code, and he attributes it to Rich Schroeppel.
1410Sstevel@tonic-gate  */
1420Sstevel@tonic-gate #define	F(b,c,d)	((((c) ^ (d)) & (b)) ^ (d))
1430Sstevel@tonic-gate #define G(b,c,d)	(((b) & (c)) | ((b) & (d)) | ((c) & (d)))
1440Sstevel@tonic-gate #define	H(b,c,d)	((b) ^ (c) ^ (d))
1450Sstevel@tonic-gate 
1460Sstevel@tonic-gate #define R0(a,b,c,d,k,s,t) { \
1470Sstevel@tonic-gate 	a+=((k)+(t)+F((b),(c),(d))); \
1480Sstevel@tonic-gate 	a=ROTATE(a,s); };
1490Sstevel@tonic-gate 
1500Sstevel@tonic-gate #define R1(a,b,c,d,k,s,t) { \
1510Sstevel@tonic-gate 	a+=((k)+(t)+G((b),(c),(d))); \
1520Sstevel@tonic-gate 	a=ROTATE(a,s); };\
1530Sstevel@tonic-gate 
1540Sstevel@tonic-gate #define R2(a,b,c,d,k,s,t) { \
1550Sstevel@tonic-gate 	a+=((k)+(t)+H((b),(c),(d))); \
1560Sstevel@tonic-gate 	a=ROTATE(a,s); };
157