Search the Community
Showing results for tags 'solution'.
Hey all, I found myself in the situation that any matchless payloads I wrote (e.g. payloads without a MATCH sequence) would not run on boot of the Key Croc. I tried many things, like setting ATTACKMODE HID with and without specific hardware properties, attaching a keyboard even though it should not be necessary etc. Nothing worked. While debugging I found the matchless payload detection in the "croc_framework" file (/usr/local/croc/bin) being badly implemented. The grep would not reliably detect non-match payloads and also did not take into account commented lines (#) or whitespace. This can be found in line 538 in the function execute_non_match_payloads() in the original 06/2020 firmware. The original line 538 is: for p in $(find /root/udisk/payloads -type f | xargs grep -c 'MATCH'|grep 0$|cut -d':' -f1) Replace it with: for p in $(find /root/udisk/payloads -type f | xargs grep -cHP '^(?=[\s]*+[^#])[^#]*(MATCH)' | grep 0$ | cut -d':' -f1) ... and now find yourself with working matchless payloads! For me, these are really important and provide great use cases. Best regards, lartsch
How does your duck setup look :) I use a bigger USB Storage device now other than the shown ( the top one of the type "SanDisk") because the shown one is only USB2 and the new USB3 one I got also flashes red when it receives data - so now i know when i can remove the hub without losing data. How does your setup look ?