Fixed run errors for runpayload.sh on windows - #699
Conversation
I didn't test if the issues happened on UNIX boxes, but any attempt to use this before would cause unreadable USB errors on windows. It works the same from the payload side, but works now
|
For context, I ran into the need to make these changes with: as the contents of my switch1/payload.txt My laptop with Linux is in the shop so I can't test if this messes up usage on UNIX systems but it works on windows now |
|
Because this is changes to anther authors payload, it is required that the original author @thedragonkeeper reviews and approved the changes. |
|
looking through the changes apart from the excessive commented lines the only actual change seems to be the addition of: All this change does is remove the extra return carriages some windows editors add to files and i dont think would cause "unreadable USB errors on windows" i think its best to remove these returns for all files when using them on a Linux system, for various reasons. |
|
Fully forgot to remove all those extra comments. I included em just for my own debugging to figure out why it wasn't working on Windows. I gave it a test on Linux and Windows and it would only work on Windows if I included the |
|
the bash bunny has a linux OS that runs the payloads , plugging it into windows or linux should make no difference in its execution. so in theory stripping the return carriages when you transfer the files over should also fix the problem youre having |
|
Didn't even think about that. I'll give it another test when I get the chance |
I didn't test if the issues happened on UNIX boxes, but any attempt to use this before would cause unreadable USB errors on windows. It works the same from the payload side, but works now