Updating the commitment and trace

This must be done after any changes that affect the attacker program.

# Build the attacker program
../scripts/build_scuttlebutt_attacker_cbor

# Update the commitment based on the new attacker program
COMMITMENT_TOOL=$PWD/../witness-checker/target/release/commitment_tool \
    python3 update_commitment.py ../out/scuttlebutt/ssb-attacker.cbor
# Generate new trace to match the new commitment and seed
./record.sh

Changing communication trace length

Update the size parameters in src/comm_trace_types.rs, and also update the definition of params in record.sh. Then run ./record.sh dummy to generate a new secrets-dummy/lib.rs that uses the new parameters.

Native builds

cargo run --features constants,secrets,inline-secrets --bin victim
cargo run --features constants,secrets,inline-secrets --bin attacker
cargo run --features constants,secrets,inline-secrets --bin checker