diff options
| author | Guy Harris <guy@alum.mit.edu> | 2012-10-24 04:03:58 +0000 |
|---|---|---|
| committer | Guy Harris <guy@alum.mit.edu> | 2012-10-24 04:03:58 +0000 |
| commit | 3ceef88b49a2d12172c9714c8adab06acf00cacc (patch) | |
| tree | babf5eef6c5ef385c2bf808f2b065875a7a89af6 | |
| parent | 4e3ddfc4c1916f5df393fdc27534630082252ca0 (diff) | |
| download | wireshark-3ceef88b49a2d12172c9714c8adab06acf00cacc.tar.gz | |
No, it's not necessarily the case that a malformed frame will only occur
during fuzz testing or randpkt testing; somebody might be putting bad
packets on the wire to try to, for example, crash or break into your
protocol implementation.
svn path=/trunk/; revision=45749
| -rw-r--r-- | epan/dissectors/packet-opensafety.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/epan/dissectors/packet-opensafety.c b/epan/dissectors/packet-opensafety.c index 869b619a60..71d03afb3c 100644 --- a/epan/dissectors/packet-opensafety.c +++ b/epan/dissectors/packet-opensafety.c @@ -1357,7 +1357,6 @@ opensafety_package_dissector(const gchar *protocolName, const gchar *sub_diss_ha while ( frameOffset < length ) { - /** This case can occurs only during fuzztest or randpkt testing. */ if ( ( length - frameOffset ) <= 0 ) break; |