Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug report: To HexDump: End of Line Sequence Detection #1860

Open
ssnkhan opened this issue Jul 10, 2024 · 0 comments
Open

Bug report: To HexDump: End of Line Sequence Detection #1860

ssnkhan opened this issue Jul 10, 2024 · 0 comments
Labels

Comments

@ssnkhan
Copy link

ssnkhan commented Jul 10, 2024

Describe the bug
Recently, when dropping binary files and using the To Hexdump module, the output pane will default to Form Feed (FF (detected). The result is that the Hex view is printed as a single line, and requires the output to be manually set to Line Feed.

To Reproduce
Steps to reproduce the behaviour or a link to the recipe / input used to cause the bug:

  1. Open a binary file, such as a PE
  2. Drag the To Hexdump module
  3. View the output pane -- note the End of Line Sequence, which will default to Line Feed

Expected behaviour
Hex view should output correctly in the standard Hex view, without need to manually change the Line Sequence.

Screenshots
Current Behaviour
Screenshot 2024-07-10 at 10 54 38

Previous (Expected) Behaviour
Screenshot 2024-07-10 at 11 01 04

Desktop (if relevant, please complete the following information):

  • OS: macOS
  • Browser: Safari Version 17.5 (19618.2.12.11.6)
  • CyberChef version: Official web service at https://gchq.github.io, Version 10.19.0

Additional context
The "Previous (Expected) Behaviour" used to be the default behaviour as far as I can remember.

@ssnkhan ssnkhan added the bug label Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant