You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to report a bug in the MSF Venom Builder. When copying the generated payload to the clipboard, commas appear between each value, which can cause issues when trying to use the payload in other tools or scripts.
Steps to reproduce:
Launch the MSF Venom Builder.
Select the desired payload and options.
Click the "Copy to Clipboard" button for msf venom command.
Paste the clipboard contents into a text editor or other tool.
Expected result:
The generated payload should be copied to the clipboard without any extra characters or formatting.
Actual result:
Commas appear between each value of the generated payload when it is copied to the clipboard.
This bug can be frustrating and time-consuming to work around, and I would appreciate it if the developers could investigate and fix the issue as soon as possible.
Thank you for your attention to this matter.
The text was updated successfully, but these errors were encountered:
Thank you for taking the time to report the bug. We have fixed the issue in our latest release, and you can find the commit with the fix at this link: 6f64b1f
Hello,
I would like to report a bug in the MSF Venom Builder. When copying the generated payload to the clipboard, commas appear between each value, which can cause issues when trying to use the payload in other tools or scripts.
Steps to reproduce:
Expected result:
The generated payload should be copied to the clipboard without any extra characters or formatting.
Actual result:
Commas appear between each value of the generated payload when it is copied to the clipboard.
This bug can be frustrating and time-consuming to work around, and I would appreciate it if the developers could investigate and fix the issue as soon as possible.
Thank you for your attention to this matter.
The text was updated successfully, but these errors were encountered: