paupaulaz Posted January 1 Share Posted January 1 After reading the documentation, I am not sure how is one supposed to connect the new RubberuDucky to a computer without triggering the payload. Is there a way the button might help with this ? If so, I could not figure it out, and was not able to plug the RubberDucky without my payload being executed first... Thanks a lot for any help ! Quote Link to comment Share on other sites More sharing options...
dark_pyrro Posted January 1 Share Posted January 1 Not sure what documentation you were reading, but it's quite clearly documented how to make the Ducky not go into attack mode using the button. https://docs.hak5.org/hak5-usb-rubber-ducky/button/wait_for_button_press https://docs.hak5.org/hak5-usb-rubber-ducky/unboxing-quack-start-guide#2.-mod-the-case-for-a-squeeze-to-press-button Quote Link to comment Share on other sites More sharing options...
paupaulaz Posted January 1 Author Share Posted January 1 Thanks for the fast reply ! Indeed, there is a clear documentation, but this is more about « going into attack mode using the button ». What I’d love to do is instead, like you said, « not going into attack mode using the button ». The use case would be to have the device ready to be used to trick people by dropping it somewhere for instance, but to be able to deactivate the payload using the button if needed. There would be no way to do this according to you ? thanks for your help anyways ! Quote Link to comment Share on other sites More sharing options...
dark_pyrro Posted January 1 Share Posted January 1 4 minutes ago, paupaulaz said: « not going into attack mode using the button » That's described in the docs Quote By default, if no other button command is currently in use, pressing the button during payload execution will make the USB Rubber Ducky stop any further keystroke injection. It will then become an ordinary USB flash drive, commonly referred to as "arming mode". Quote Link to comment Share on other sites More sharing options...
paupaulaz Posted January 2 Author Share Posted January 2 for me this is still a bit different: one has to quickly enough press the button after connecting in order for the "the USB Rubber Ducky [to] stop any further keystroke injection", which is different.. Depending the payload, this could be something you would not want to run on your development machine, even for its first keystrokes before interrupting. So there's probably no solution to my exact problem but thanks a lot for pointing these workarounds anyways ! Quote Link to comment Share on other sites More sharing options...
Darren Kitchen Posted January 16 Share Posted January 16 You could always prepend your payload with the following: Quote ATTACKMODE HID STORAGE WAIT_FOR_BUTTON_PRESS This would prevent further payload execution UNTIL the button is pressed. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.