Jump to content

QUACK DELAY vs Bash sleep


Recommended Posts

Is there an effective difference between "QUACK DELAY 1000" vs "sleep 1"?  I have a payload which simply needs to delay for a time, but I can't see any benefit to using QUACK versus 'sleep' on the Bash Bunny.  I know QUACK DELAY is from back on the Rubber Ducky, so Ducky Script is going to include it.  I'm just curious if there's a reason for one vs another on the BB.



Link to comment
Share on other sites

I would say; not really. The sleep command is bash (as you've already mentioned) and 'QUACK DELAY' is the Python 'time' module using the 'sleep' method/function (i.e. 'time.sleep'). I guess it's a matter of "clean coding". If the majority of the payload was Ducky Script, I would probably use 'QUACK DELAY' instead of entering a few bash commands here and there, just to keep it more consistent and readable. If it was more mixed, I would go with whatever feels good/appropriate at the moment. If there were blocks of script code in the same payload, I would probably use 'QUACK DELAY' in Ducky script blocks and 'sleep' in bash blocks. Makes it easier if I want to transfer payload blocks and re-use them on other devices, such as the Ducky (need to get rid of the QUACKs though).

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...