Support context.timeout
in ~/.pwn.conf
#2592
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(Tested on 4.14.1, unclear when this regression occurred.)
It appears
context.timeout
cannot be set in ~/.pwn.conf, even though the docs indicate that it can.Example ~/.pwn.conf:
This patch fixes this by adding
float
to the list of types that are allowable to besafeeval
'd inupdate_context_defaults
, which does not seem like it should cause issues (although I am new to the codebase, please correct me if I am mistaken).Perhaps this has slid under the radar because
timeout
is the only member of context that is affected by this: