-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement fuzz testing #97
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,3 +4,5 @@ | |
tags | ||
*DS_Store | ||
*.patch | ||
mappings/ | ||
NVChip |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,63 @@ | ||
#!/usr/bin/env bash | ||
|
||
# ------------------------------------------------------------------------------ | ||
# Copyright (c) 2020, Arm Limited, All Rights Reserved | ||
# SPDX-License-Identifier: Apache-2.0 | ||
# | ||
# Licensed under the Apache License, Version 2.0 (the "License"); you may | ||
# not use this file except in compliance with the License. | ||
# You may obtain a copy of the License at | ||
# | ||
# http:#www.apache.org/licenses/LICENSE-2.0 | ||
# | ||
# Unless required by applicable law or agreed to in writing, software | ||
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT | ||
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
# See the License for the specific language governing permissions and | ||
# limitations under the License. | ||
# ------------------------------------------------------------------------------ | ||
|
||
FUZZ_CONTAINER_NAME=parsec_fuzzer | ||
CLEANUP_CONTAINER_NAME=parsec_fuzzer_cleanup | ||
|
||
set -e | ||
|
||
if [[ "$1" == "run" ]] | ||
then | ||
# Set up fuzz folder | ||
docker run --rm -v $(pwd):/parsec -w /parsec/fuzz --name $CLEANUP_CONTAINER_NAME parsec/fuzz ./cleanup.sh | ||
# A copy of the config file is used because the file is modified during the run | ||
cp fuzz/config.toml fuzz/run_config.toml | ||
|
||
# Build Docker image | ||
docker build fuzz/docker -t parsec/fuzz | ||
|
||
# Stop previous container and run fuzzer | ||
docker kill $FUZZ_CONTAINER_NAME || true | ||
sleep 5s | ||
docker run -d --rm -v $(pwd):/parsec -w /parsec/fuzz --name $FUZZ_CONTAINER_NAME parsec/fuzz ./run_fuzz.sh | ||
elif [[ "$1" == "stop" ]] | ||
then | ||
docker kill $FUZZ_CONTAINER_NAME | ||
elif [[ "$1" == "follow" ]] | ||
then | ||
docker logs -f --tail 100 $FUZZ_CONTAINER_NAME | ||
elif [[ "$1" == "clean" ]] | ||
then | ||
# Cleanup is done via Docker because on some systems ACL settings prevent the user who | ||
# created a container from removing the files created by said container. Another one | ||
# is needed to do the cleanup. | ||
docker run -d --rm -v $(pwd):/parsec -w /parsec/fuzz --name $CLEANUP_CONTAINER_NAME parsec/fuzz ./cleanup.sh | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. well yes, but no. if you try that on your server, in the parsec account, you'll see why :) when docker runs, it runs as root, so removing new files isn't possible from a non-sudoer account, unless you do something from a container again There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'll add a comment! There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks for the info! |
||
elif [[ "$1" == "erase" ]] | ||
then | ||
docker run -d --rm -v $(pwd):/parsec -w /parsec/fuzz -e "ERASE=true" --name $CLEANUP_CONTAINER_NAME parsec/fuzz ./cleanup.sh | ||
else | ||
echo "usage: ./fuzz.sh [COMMAND] | ||
|
||
Commands: | ||
'run' - builds the fuzzing container and runs the fuzzer | ||
'stop' - stops the fuzzing container | ||
'follow' - prints and follows the log output of the fuzzing container | ||
'clean' - clean up the fuzzing environment (does not remove artifacts or the fuzz corpus) | ||
'erase' - fully clean the fuzzing environment - WARNING: this will remove all the results of previous runs" | ||
fi |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
|
||
target | ||
corpus | ||
artifacts | ||
*.log | ||
run_config.toml | ||
NVChip |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is it needed to copy the configuration file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so that you don't have to remove the PKCS11 slot number after each use
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah makes sense! Maybe a comment would help here then