Bug report: To HexDump: End of Line Sequence Detection
- Dominant language
- JavaScript
- Stars
- 35.8k
- Forks
- 4.1k
- Avg merge
- 2d 26m
- Merged PRs (30d)
- 33
Description
**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_
_Previous (Expected) Behaviour_
**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.
Contributor guide
Research direction
Reproduce the issue with a binary file such as a PE, then use the To Hexdump module and inspect the output pane's End of Line Sequence. Compare the detected default with the expected Line Feed behavior; done means the Hex view displays correctly without manually changing the line sequence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100