| Bug ID |
13165
|
| Summary |
Text2pcap on windows produces corrupt output
|
| Product |
Wireshark
|
| Version |
2.2.2
|
| Hardware |
x86-64
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Extras
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 2.2.2 (v2.2.2-0-g775fb08)
--
text2pcap produces corrupted capture if new line character (0A) is found, when
using pipe output.
echo 000000 0a 0a | "c:\program files\wireshark\text2pcap" - - > outfile
Expected output:
# xxd outfile
0000000: d4c3 b2a1 0200 0400 0000 0000 0000 0000 ................
0000010: ffff 0000 0100 0000 4472 3458 0000 0000 ........Dr4X....
0000020: 0200 0000 0200 0000 0a0a ..........
Actual output:
# xxd outfile
0000000: d4c3 b2a1 0200 0400 0000 0000 0000 0000 ................
0000010: ffff 0000 0100 0000 d371 3458 0000 0000 .........q4X....
0000020: 0200 0000 0200 0000 0d0a 0d0a ............
Note that at the end, 0A has been replaced by 0D0A.
You are receiving this mail because:
- You are watching all bug changes.