tools/wireshark, branch v2.6.16rc0

2.6.15 → 2.6.16.

2020-02-26T22:30:33+00:00

Change-Id: I69123ff5d020fa2738961cbf57556632f5a97fc9
Reviewed-on: https://code.wireshark.org/review/36202
Reviewed-by: Gerald Combs

Build 2.6.15.

2020-02-26T20:29:40+00:00

Change-Id: I51f407e88f2b2d7ace47a8e95b649cbd35d5053f
Reviewed-on: https://code.wireshark.org/review/36198
Reviewed-by: Gerald Combs

EAP: Remove a couple of string length assumptions.

2020-02-24T14:53:23+00:00

Don't assume our MNC and MCC string lengths are > 3.

Bug: 16397
Change-Id: I0759dcb9d0c5f078cf3a98e9323d9cb741e15dd4
Reviewed-on: https://code.wireshark.org/review/36146
Reviewed-by: Gerald Combs 
Petri-Dish: Gerald Combs 
Tested-by: Petri Dish Buildbot
Reviewed-by: Anders Broman 
(cherry picked from commit 8bda8642dfc8c9a870c6a48771566012353cc898)
Reviewed-on: https://code.wireshark.org/review/36173

[Automatic update for 2020-02-23]

2020-02-23T08:58:24+00:00

Update manuf, services enterprise numbers, translations, and other items.

Change-Id: I11c1e21e2e716e190ae592e6ad135c5bc5f0a551
Reviewed-on: https://code.wireshark.org/review/36164
Reviewed-by: Gerald Combs

Use "must" instead of "should" to avoid ambiguity.

2020-02-23T04:37:10+00:00

As I said in

    https://ask.wireshark.org/question/10361/how-to-properly-use-heuristic-dissector-for-tcp/?answer=10363#post-id-10363

  "Should" has multiple meanings; there's "Used to indicate obligation,
  duty, or correctness, typically when criticizing someone's actions.", as
  in "I think we should trust our people more", and there's "Used to
  indicate what is probable.", as in "the bus should arrive in a few
  minutes". You're reading it in the latter sense; it was intended in the
  former sense.

  That sentence should probably be changed to "Wireshark must be then set
  up..." to avoid the ambiguity.

Make it so (over half a year later, sigh), and change another case where
"should" is meant in the first sense while we're at it.

Change-Id: I90198d1616619c75802deeeb703ceee0c8bac1bf
Reviewed-on: https://code.wireshark.org/review/36155
Reviewed-by: Guy Harris 
(cherry picked from commit c268e9b0d563cfd248fae611c06e39430e1bad6c)
Reviewed-on: https://code.wireshark.org/review/36158

[Automatic update for 2020-02-16]

2020-02-16T08:58:58+00:00

Update manuf, services enterprise numbers, translations, and other items.

Change-Id: I2feb9bb26444e5047db077addad9b05c35582ebb
Reviewed-on: https://code.wireshark.org/review/36119
Reviewed-by: Gerald Combs

WiMax DLMAP: Fix a large loop.

2020-02-13T17:51:12+00:00

Make sure we advance our offset.

Bug: 16383
Ping-Bug: 16368
Change-Id: I4949cb0988601dbe545d0bc22de4d654b4e61204
Reviewed-on: https://code.wireshark.org/review/36085
Reviewed-by: Gerald Combs 
Petri-Dish: Gerald Combs 
Reviewed-by: Anders Broman 
(cherry picked from commit 6dad599a8a1bda8b8e999cc4a7e460140e4ecc0a)
Reviewed-on: https://code.wireshark.org/review/36094

[Automatic update for 2020-02-09]

2020-02-09T08:58:24+00:00

Update manuf, services enterprise numbers, translations, and other items.

Change-Id: Ib29ea40d51b569f366ad46ba979f7e9b974df29f
Reviewed-on: https://code.wireshark.org/review/36063
Reviewed-by: Gerald Combs

WiMax DLMAP: Add a length check.

2020-02-07T19:59:31+00:00

Make sure we have enough data for a CRC.

Bug: 16368
Change-Id: I03a2532061a5cf5e28cb65c83dd4ab90654d1679
Reviewed-on: https://code.wireshark.org/review/36051
Reviewed-by: Gerald Combs

[Automatic update for 2020-02-02]

2020-02-02T08:58:31+00:00

Update manuf, services enterprise numbers, translations, and other items.

Change-Id: I5c054a84cb1d2b34901306e7079fdebbb5f55c24
Reviewed-on: https://code.wireshark.org/review/36008
Reviewed-by: Gerald Combs