v1.7

Full release for parallel execution

Variable Behavior

If sequences are executed with the x-stepper-execute-before or x-stepper-execute-after header, the execution does not update the global or variables stored with the sequence. However, in the entire sequence (requests before, the actual request with the stepper header, and the requests afterwards) all use the up-to-date variables as retrieved in this execution. Meaning, the stepper UI is now separate from the before and after sequences. These are executed completely different, isolating the UI from the actual execution and allowing stepper to be used with full parallelism. This allows stepper to work with multi-threaded tools like Intruder or Active Scanner without dropped requests.

As interactions are complex, this is potentially not completely bug-free. So further testing must be done.

Fixes

This release also fixes the issues of version 1.6 where sequences could not be exported or imported and do not persist after closing Burp.