s_o_r_c_e_r_e_r Posted October 17, 2017 Share Posted October 17, 2017 (edited) I have this strange quacking behaviour: When i output to notepad, This line is quacking just fine:Q STRING ipconfig /all \> f:\\loot\\test.doc This line is not quacking at all:Q STRING ipconfig /all \> f:\\loot\\test.txt Is this a bug, or am I totally overlooking something? This is my simple test script: LED SETUP ATTACKMODE HID DUCKY_LANG no Q STRING ipconfig all \> f:\\loot\\test.doc Q ENTER Q STRING ipconfig all \> f:\\loot\\test.txt Q ENTER LED G 100 I am on version : 1.3_267 Any help would be greatly appreciated. Edited October 17, 2017 by s_o_r_c_e_r_e_r Quote Link to comment Share on other sites More sharing options...
uintdev Posted October 17, 2017 Share Posted October 17, 2017 Have you tried putting the commands in quotes? For example: Q STRING "foobar" Quote Link to comment Share on other sites More sharing options...
s_o_r_c_e_r_e_r Posted October 17, 2017 Author Share Posted October 17, 2017 Ok, this just make no sense at all. To me it seems like it is the ending "txt" that is the problem, because "doc" works fine, and even "tx" will work. I am totally lost here. Of cause I could just go with another file extension than "txt", but this is not how it should work. Here are the results of the different suggestions you made: LED SETUP ATTACKMODE HID DUCKY_LANG no Q STRING ipconfig all \> f:\\loot\\test.doc Q ENTER Q STRING ipconfig all \> f:\\loot\\test.txt Q ENTER LED G 1000 Result: ipconfig all > f:\loot\test.doc LED SETUP ATTACKMODE HID DUCKY_LANG no Q STRING ipconfig all \> f:\\loot\\test.txt Q ENTER Q STRING ipconfig all \> f:\\loot\\test.doc Q ENTER LED G 1000 Result: ipconfig all > f:\loot\test.doc LED SETUP ATTACKMODE HID DUCKY_LANG no Q STRING "ipconfig all \> f:\\loot\\test.txt" Q ENTER Q STRING "ipconfig all \> f:\\loot\\test.doc" Q ENTER LED G 1000 Result: ipconfig all \> f:\loot\test.doc Quote Link to comment Share on other sites More sharing options...
Dave-ee Jones Posted October 17, 2017 Share Posted October 17, 2017 Try putting them in the ' quotes, father than ". ' means that anything inside them is "escaped" as a bash character. It could be that it thinks your exiting the command, and if so putting them in the singluar quotation marks ( ' ' ) should help escape them. Quote Link to comment Share on other sites More sharing options...
Sebkinne Posted October 18, 2017 Share Posted October 18, 2017 You need to put it in quotes. An argument ending in .txt is going to be interpreter as ducky script. Not really a bug, but something we can work around in a future update. Quote Link to comment Share on other sites More sharing options...
s_o_r_c_e_r_e_r Posted October 18, 2017 Author Share Posted October 18, 2017 Ok. I did a new test and put every line in single quotes, but the line ending with ".txt" is still not showing? LED SETUP ATTACKMODE HID DUCKY_LANG no Q STRING 'test.tx' Q ENTER Q STRING 'test.xt' Q ENTER Q STRING 'test.txt' Q ENTER Q STRING 'test.doc' Q ENTER LED G 1000 Result: test.tx test.xt test.doc Quote Link to comment Share on other sites More sharing options...
Sebkinne Posted October 18, 2017 Share Posted October 18, 2017 Interesting. If I can confirm this issue, we'll get it fixed and pushed out Friday. 2 Quote Link to comment Share on other sites More sharing options...
s_o_r_c_e_r_e_r Posted October 18, 2017 Author Share Posted October 18, 2017 Yes, as a workaround for now that actually works. Thanks! 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.