Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Pick up FIPS-140 certification work.
This consists of the following: 1)Move FIPS integrity and post tests to dll load time. 2) Extra data clearing of CPS, change to the prime check requirements. 3) Allow FIPS level 1. This is detected by whether or not there is a password on the database. 4) Update fipstest to handle new tests and the latest formats used by NIST. Also make running of the tests automated. bob
- Loading branch information
Showing
58 changed files
with
5,742 additions
and
3,737 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,67 @@ | ||
#!/bin/sh | ||
# | ||
# This Source Code Form is subject to the terms of the Mozilla Public | ||
# License, v. 2.0. If a copy of the MPL was not distributed with this | ||
# file, You can obtain one at http://mozilla.org/MPL/2.0/. | ||
# | ||
# A Bourne shell script for running the NIST AES Algorithm Validation Suite | ||
# | ||
# Before you run the script, set your PATH, LD_LIBRARY_PATH, ... environment | ||
# variables appropriately so that the fipstest command and the NSPR and NSS | ||
# shared libraries/DLLs are on the search path. Then run this script in the | ||
# directory where the REQUEST (.req) files reside. The script generates the | ||
# RESPONSE (.rsp) files in the same directory. | ||
|
||
BASEDIR=${1-.} | ||
TESTDIR=${BASEDIR}/AES_GCM | ||
COMMAND=${2-run} | ||
REQDIR=${TESTDIR}/req | ||
RSPDIR=${TESTDIR}/resp | ||
|
||
gcm_decrypt_requests=" | ||
gcmDecrypt128.req | ||
gcmDecrypt192.req | ||
gcmDecrypt256.req | ||
" | ||
|
||
gcm_encrypt_extiv_requests=" | ||
gcmEncryptExtIV128.req | ||
gcmEncryptExtIV192.req | ||
gcmEncryptExtIV256.req | ||
" | ||
gcm_encrypt_intiv_requests=" | ||
" | ||
|
||
#gcm_encrypt_intiv_requests=" | ||
#gcmEncryptIntIV128.req | ||
#gcmEncryptIntIV192.req | ||
#gcmEncryptIntIV256.req | ||
#" | ||
|
||
if [ ${COMMAND} = "verify" ]; then | ||
for request in $gcm_decrypt_requests $gcm_encrypt_extiv_requests; do | ||
sh ./validate1.sh ${TESTDIR} $request ' ' '-e /Reason:/d' | ||
done | ||
for request in $gcm_encrypt_intiv_requests; do | ||
name=`basename $request .req` | ||
echo ">>>>> $name" | ||
fipstest aes gcm decrypt ${RSPDIR}/$name.rsp | grep FAIL | ||
done | ||
exit 0 | ||
fi | ||
|
||
for request in $gcm_decrypt_requests; do | ||
response=`echo $request | sed -e "s/req/rsp/"` | ||
echo $request $response | ||
fipstest aes gcm decrypt ${REQDIR}/$request > ${RSPDIR}/$response | ||
done | ||
for request in $gcm_encrypt_intiv_requests; do | ||
response=`echo $request | sed -e "s/req/rsp/"` | ||
echo $request $response | ||
fipstest aes gcm encrypt_intiv ${REQDIR}/$request > ${RSPDIR}/$response | ||
done | ||
for request in $gcm_encrypt_extiv_requests; do | ||
response=`echo $request | sed -e "s/req/rsp/"` | ||
echo $request $response | ||
fipstest aes gcm encrypt_extiv ${REQDIR}/$request > ${RSPDIR}/$response | ||
done |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.