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
This is not a bug, the plaintext input has a dash between two characters, which per the tool documentation is used to describe a range of bytes. To get the result you want, you need to escape the special character (-) by prefixing it with a \. The plaintext should be .\-_ and the cipher text can remain the same because the dash is at the end, not between two characters.
A substitution cipher allowing you to specify bytes to replace with other byte values. This can be used to create Caesar ciphers but is more powerful as any byte value can be substituted, not just letters, and the substitution values need not be in order.
Enter the bytes you want to replace in the Plaintext field and the bytes to replace them with in the Ciphertext field.
Non-printable bytes can be specified using string escape notation. For example, a line feed character can be written as either \n or \x0a.
Byte ranges can be specified using a hyphen. For example, the sequence 0123456789 can be written as 0-9.
Note that blackslash characters are used to escape special characters, so will need to be escaped themselves if you want to use them on their own (e.g.\\).
Describe the bug
When using substitution, cyberchef is unable to produce the following decrypted ciphertext.
.-_
should become,_.-
but instead becomes_-_
and warns that the ciphertext and plaintext are different.To Reproduce
Steps to reproduce the behaviour or a link to the recipe / input used to cause the bug:
https://gchq.github.io/CyberChef/#recipe=Substitute('.-_','_.-',true)&input=Li1f
Expected behaviour
I expect the output
_.-
Screenshots
The text was updated successfully, but these errors were encountered: