1 ====================================================================
2 Written by Andy Polyakov <appro@fy.chalmers.se> for the OpenSSL
3 project. The module is, however, dual licensed under OpenSSL and
4 CRYPTOGAMS licenses depending on where you obtain it. For further
5 details see http://www.openssl.org/~appro/cryptogams/.
6 ====================================================================
8 Copyright (c) 2006-2012, CRYPTOGAMS by <appro@openssl.org>
11 Redistribution and use in source and binary forms, with or without
12 modification, are permitted provided that the following conditions
15 * Redistributions of source code must retain copyright notices,
16 this list of conditions and the following disclaimer.
18 * Redistributions in binary form must reproduce the above
19 copyright notice, this list of conditions and the following
20 disclaimer in the documentation and/or other materials
21 provided with the distribution.
23 * Neither the name of the CRYPTOGAMS nor the names of its
24 copyright holder and contributors may be used to endorse or
25 promote products derived from this software without specific
26 prior written permission.
28 ALTERNATIVELY, provided that this notice is retained in full, this
29 product may be distributed under the terms of the GNU General Public
30 License (GPL), in which case the provisions of the GPL apply INSTEAD OF
33 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER AND CONTRIBUTORS
34 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
35 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
36 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
37 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
38 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
39 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
40 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
41 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
42 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
43 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
46 ######################################################################
47 ## Constant-time SSSE3 AES core implementation.
50 ## By Mike Hamburg (Stanford University), 2009
53 ## For details see http://shiftleft.org/papers/vector_aes/ and
54 ## http://crypto.stanford.edu/vpaes/.