Skip to content

Fix target DisableNops not being passed to payload#10591

Merged
wchen-r7 merged 1 commit intorapid7:masterfrom
wvu:bug/nop
Sep 6, 2018
Merged

Fix target DisableNops not being passed to payload#10591
wchen-r7 merged 1 commit intorapid7:masterfrom
wvu:bug/nop

Conversation

@wvu
Copy link
Contributor

@wvu wvu commented Sep 5, 2018

DisableNops doesn't work in a target, but Space and other related options do, so there is no straightforward way to avoid NOP generation in a target with a space restriction.

Please see #9892 and #9898 for context.

  • Set DisableNops in a target with Space (example: 'Payload' => {'Space' => 4089, 'DisableNops' => true})
  • Test to see that NOP generation was disabled

Required by #10564. cc @wchen-r7

@wchen-r7
Copy link
Contributor

wchen-r7 commented Sep 6, 2018

Seems to be ok. If I have space that's 1024 bytes, and by setting DisableNops to true, payload only shrinks and not bigger. Seems safe. Will land.

@wchen-r7 wchen-r7 merged commit e2428b5 into rapid7:master Sep 6, 2018
@wchen-r7
Copy link
Contributor

wchen-r7 commented Sep 6, 2018

Release Notes

Payloads now support the DisableNops option correctly.

@wvu wvu deleted the bug/nop branch September 6, 2018 03:40
@tdoan-r7 tdoan-r7 added the rn-fix release notes fix label Sep 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug library rn-fix release notes fix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants