Skip tests if p5-BSD-Socket-Splice is not installed.

Quote SUDO value during propagation, allowing `doas -n' to be correctly
honored which I use while running regress. The same principle is already
applied to the PYTHON variable here.

py3-scapy is now scapy

OK bluhm sthen

Switch to scapy with python 3.

Remove echo headlines.

Do not create files as dependency of .BEGIN rule. Noticed by
deraadt@ with make obj in regress.

Rework when tests have to be skipped due to insufficient configuration
of the regress machine.

Simplify the detection for installed python and scapy. Refactor
these tests to make them similar. Use the setup and cleanup
variables.

Insert a rule into pf regress anchor that passes all packets without
state. The default pf rules interfere with this scapy test.

Fix the glob to find all scapy test scripts.

I am trying to find a bug that seems to be triggered by a combination
of TCP timing and socket splicing. Add tests that use Scapy scripts
as client and server. That allows to drop, delay and retransmit
single TCP packets to execute various code paths in the remote
OpenBSD stack.

Quote SUDO value during propagation, allowing `doas -n' to be correctly
honored which I use while running regress. The same principle is already
applied to the PYTHON variable here.

py3-scapy is now scapy

OK bluhm sthen

Switch to scapy with python 3.

Remove echo headlines.

Do not create files as dependency of .BEGIN rule. Noticed by
deraadt@ with make obj in regress.

Rework when tests have to be skipped due to insufficient configuration
of the regress machine.

Simplify the detection for installed python and scapy. Refactor
these tests to make them similar. Use the setup and cleanup
variables.

Insert a rule into pf regress anchor that passes all packets without
state. The default pf rules interfere with this scapy test.

Fix the glob to find all scapy test scripts.

I am trying to find a bug that seems to be triggered by a combination
of TCP timing and socket splicing. Add tests that use Scapy scripts
as client and server. That allows to drop, delay and retransmit
single TCP packets to execute various code paths in the remote
OpenBSD stack.

py3-scapy is now scapy

OK bluhm sthen

Switch to scapy with python 3.

Remove echo headlines.

Do not create files as dependency of .BEGIN rule. Noticed by
deraadt@ with make obj in regress.

Rework when tests have to be skipped due to insufficient configuration
of the regress machine.

Simplify the detection for installed python and scapy. Refactor
these tests to make them similar. Use the setup and cleanup
variables.

Insert a rule into pf regress anchor that passes all packets without
state. The default pf rules interfere with this scapy test.

Fix the glob to find all scapy test scripts.

I am trying to find a bug that seems to be triggered by a combination
of TCP timing and socket splicing. Add tests that use Scapy scripts
as client and server. That allows to drop, delay and retransmit
single TCP packets to execute various code paths in the remote
OpenBSD stack.

Switch to scapy with python 3.

Remove echo headlines.

Do not create files as dependency of .BEGIN rule. Noticed by
deraadt@ with make obj in regress.

Rework when tests have to be skipped due to insufficient configuration
of the regress machine.

Simplify the detection for installed python and scapy. Refactor
these tests to make them similar. Use the setup and cleanup
variables.

Insert a rule into pf regress anchor that passes all packets without
state. The default pf rules interfere with this scapy test.

Fix the glob to find all scapy test scripts.

I am trying to find a bug that seems to be triggered by a combination
of TCP timing and socket splicing. Add tests that use Scapy scripts
as client and server. That allows to drop, delay and retransmit
single TCP packets to execute various code paths in the remote
OpenBSD stack.

Remove echo headlines.

Do not create files as dependency of .BEGIN rule. Noticed by
deraadt@ with make obj in regress.

Rework when tests have to be skipped due to insufficient configuration
of the regress machine.

Simplify the detection for installed python and scapy. Refactor
these tests to make them similar. Use the setup and cleanup
variables.

Insert a rule into pf regress anchor that passes all packets without
state. The default pf rules interfere with this scapy test.

Fix the glob to find all scapy test scripts.

I am trying to find a bug that seems to be triggered by a combination
of TCP timing and socket splicing. Add tests that use Scapy scripts
as client and server. That allows to drop, delay and retransmit
single TCP packets to execute various code paths in the remote
OpenBSD stack.

Do not create files as dependency of .BEGIN rule. Noticed by
deraadt@ with make obj in regress.

Rework when tests have to be skipped due to insufficient configuration
of the regress machine.

Simplify the detection for installed python and scapy. Refactor
these tests to make them similar. Use the setup and cleanup
variables.

Insert a rule into pf regress anchor that passes all packets without
state. The default pf rules interfere with this scapy test.

Fix the glob to find all scapy test scripts.

I am trying to find a bug that seems to be triggered by a combination
of TCP timing and socket splicing. Add tests that use Scapy scripts
as client and server. That allows to drop, delay and retransmit
single TCP packets to execute various code paths in the remote
OpenBSD stack.

Rework when tests have to be skipped due to insufficient configuration
of the regress machine.

Simplify the detection for installed python and scapy. Refactor
these tests to make them similar. Use the setup and cleanup
variables.

Insert a rule into pf regress anchor that passes all packets without
state. The default pf rules interfere with this scapy test.

Fix the glob to find all scapy test scripts.

I am trying to find a bug that seems to be triggered by a combination
of TCP timing and socket splicing. Add tests that use Scapy scripts
as client and server. That allows to drop, delay and retransmit
single TCP packets to execute various code paths in the remote
OpenBSD stack.

Simplify the detection for installed python and scapy. Refactor
these tests to make them similar. Use the setup and cleanup
variables.

Insert a rule into pf regress anchor that passes all packets without
state. The default pf rules interfere with this scapy test.

Fix the glob to find all scapy test scripts.

I am trying to find a bug that seems to be triggered by a combination
of TCP timing and socket splicing. Add tests that use Scapy scripts
as client and server. That allows to drop, delay and retransmit
single TCP packets to execute various code paths in the remote
OpenBSD stack.

Insert a rule into pf regress anchor that passes all packets without
state. The default pf rules interfere with this scapy test.

Fix the glob to find all scapy test scripts.

I am trying to find a bug that seems to be triggered by a combination
of TCP timing and socket splicing. Add tests that use Scapy scripts
as client and server. That allows to drop, delay and retransmit
single TCP packets to execute various code paths in the remote
OpenBSD stack.