-
Notifications
You must be signed in to change notification settings - Fork 260
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.
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
payloads: web-related, incl. probes.encoding
migration
#933
Conversation
probes.encoding
migrationprobes.encoding
migration
… reduce volume of payload scans
Lets consider making the exposed entry point for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it make sense to have consistent DEFAULT_PARAMS
naming as payload_name
? Examples of impact noted in the review.
Also looking at this payload_trigger
being populated directly with the payloads
set seems non-intuitive, but I don't have a better alternative to offer at this time so reasonable to live with for now.
Co-authored-by: Jeffrey Martin <[email protected]> Signed-off-by: Leon Derczynski <[email protected]>
Co-authored-by: Jeffrey Martin <[email protected]> Signed-off-by: Leon Derczynski <[email protected]>
Factor out web-related payloads, and complete the transition to
garak.payloads
use inprobes.encoding
Verification
garak -m test -g 1 -p encoding,latentinjection,xss
and check thereport.jsonl
s include appropriate payload textpython -m pytest tests/test_payloads.py
python -m pytest tests/probes/test_probes_encoding.py
python -m pytest tests/probes/test_probes_latentinjection.py