Wireshark-bugs: [Wireshark-bugs] [Bug 8221] Large SABP messages are not getting decoded
Tomas Kukosa
changed
bug 8221
| What |
Removed |
Added |
| CC |
|
tomas.kukosa@unify.com
|
Comment # 11
on bug 8221
from Tomas Kukosa
(In reply to comment #10)
>
> And the way I understand, length determinant == Number of bytes passed from
> TCP to SABP. Am I right?
Not exactly, it depends how the SABP message is defined in ASN.1. The length
indicator is used at many various places inside message with different
meanings. It could be number of octets, number of bits, number of characters,
etc.
We are quite lucky with SABP message that the 1st length indicator is used
quite early on fixed place (at the 4th octet) and determines whole rest of the
message.
Maybe the implementation would not be so complicated if we simplify it a little
bit.
1) support just for fragmented types with fixed element size (bit, octet)
2) when PER decoding is called the PDU must be already reassembled
3) offer SABP some function instead of dissect_per_length_determinant() which
returns complete length (length indicator + content) or indication that more
data are necessary
You are receiving this mail because:
- You are watching all bug changes.
