You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the BadUSB module, any line containing accents (é, è, etc.), commas, or other special characters fails to execute correctly. The input gets cut off or behaves unexpectedly. This seems to be due to encoding or parsing issues with non-ASCII characters. A workaround is to avoid accents and punctuation entirely, but a fix would be appreciated.
Reproduction
Create a BadUSB payload with the following line:
"STRING Bonjour, je m’appelle Jean et j’apporterai des pâtisseries dès demain."
Run the payload via:
BadUSB app on Flipper Zero
Script placed in /badusb/ folder and launched manually with fr_FR layout
Expected behavior:
The full sentence is typed out with all characters, including accents and commas.
Actual behavior:
The script stops at the first special character (like ’, é, è, à, or ,)
Target
No response
Logs
On the flipper, the script stop and say 'ERROR: line 7 : No Keycode defined for "'
Anything else?
No response
The text was updated successfully, but these errors were encountered:
unfortunately, a fix is not viable. the whole keyboard layout system and the scripting language are made around ascii characters. you should try to avoid non-ascii characters, or find alternative ways to type them like escaping characters in a shell prompt.
Describe the bug.
When using the BadUSB module, any line containing accents (é, è, etc.), commas, or other special characters fails to execute correctly. The input gets cut off or behaves unexpectedly. This seems to be due to encoding or parsing issues with non-ASCII characters. A workaround is to avoid accents and punctuation entirely, but a fix would be appreciated.
Reproduction
BadUSB app on Flipper Zero
Script placed in /badusb/ folder and launched manually with fr_FR layout
Target
No response
Logs
Anything else?
No response
The text was updated successfully, but these errors were encountered: