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
Is your feature request related to a problem? Please describe.
I forgot to switch the XOR key input field from hex to UTF8. Ideally, CyberChef would have warned if the input contains non-whitespace, non-[0123456789abcdef] inputs.
Hello, I would like to attempt to fix this issue. I looked through the changes in #1975 and it seems relatively simple to alter the xor to give a warning when there are non-hex characters in the hex input. I think this would help alleviate some of the confusion that led to this issue.
Is your feature request related to a problem? Please describe.
I forgot to switch the XOR key input field from hex to UTF8. Ideally, CyberChef would have warned if the input contains non-whitespace, non-[0123456789abcdef] inputs.
https://cyberchef.org/#recipe=XOR(%7B'option':'Hex','string':'Why%20is%20this%20allowed'%7D,'Standard',false)&input=U29tZSB0ZXN0IHN0cmluZw
Describe the solution you'd like
A warning or something would be nice to see
Additional context
Wasted like 2h in flare-on because of this 🙃
The text was updated successfully, but these errors were encountered: