Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Running system under test from tlsfuzzer #46

Open
tomato42 opened this issue Jul 11, 2016 · 0 comments
Open

Running system under test from tlsfuzzer #46

tomato42 opened this issue Jul 11, 2016 · 0 comments
Labels
complex Issues that require good knowledge of tlsfuzzer internals enhancement new feature to be implemented
Milestone
v1.0.0

Comments

@tomato42
Copy link
Member

tomato42 commented Jul 11, 2016 •
edited

Allow the tlsfuzzer to run the SUT by itself, needed to run the SUT with valgrind or to collect core files.

While the tests/scripts_retention.py essentially can do that, it's quite stupid about it – can't select key files (or generate them itself on demand), restart the server when it crashes, etc.

depends on #58
@tomato42 tomato42 added the enhancement new feature to be implemented label Jul 11, 2016
@tomato42 tomato42 added this to the v1.0.0 milestone Jul 11, 2016
@tomato42 tomato42 mentioned this issue Feb 13, 2018
Open
@tomato42 tomato42 added the complex Issues that require good knowledge of tlsfuzzer internals label May 2, 2018
@tomato42 tomato42 mentioned this issue Dec 19, 2018
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
complex Issues that require good knowledge of tlsfuzzer internals enhancement new feature to be implemented
Projects
None yet
Milestone
v1.0.0
Development

No branches or pull requests
1 participant
@tomato42