[Wireshark-dev] Release lifetime and version number changes?

[Gerald Combs]

We currently have three active release branches: 3.0, 2.6, and 2.4. This is 
because we support each release branch for a set amount of time (typically 24 
months after the initial .0 release) and our last three .0 releases were less 
than 12 months apart. However, having many active branches can sometimes cause 
confusion[1] and far fewer people download the "Old Old Stable" release than 
the "Old Stable" or "Stable" releases. Would it make sense to have only two 
release branches active at any given time, e.g. by adjusting our release branch 
lifetimes to "24 months or whenever we have two newer active branches, 
whichever comes first"?

We've also been using odd minor numbers for development releases and even minor 
numbers for stable releases[2] for many years now. We don't make very many 
development releases and instead tend to have one or more release candidates 
after branch is created. Would it make sense to drop the even/odd scheme and 
make the next major release 3.1.0?

[1] 
https://ask.wireshark.org/question/8433/why-are-multiple-versions-released-at-once/
[2] https://wiki.wireshark.org/Development/ReleaseNumbers
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] IKEv2/ESP decryption preference inconsistency

[Michael Lum]

Hi,

we just started trying to decrypt IKE/ESP packages and have it working 
successfully but
found that the preference settings appear to be inconsistent.

The IKE decryption table parameters in ISAKMP for SPI and keys require that you 
NOT put
0x in front of hex values.  (It is nice that the help indicates that 
requirement.)

In the ESP SAs table the SPI and keys REQUIRE 0x in front of hex values.
(Unfortunately there is no help for that table.)

Is there a design reason for this or just two different implementors?
(Yes, I'm implying it should be consistent if there is no design reason.)

Thanks for all your hard work.

BR,

Michael

Michael Lum 
(michael@starsolutions.com) | STAR 
SOLUTIONS | Principal Software Engineer
4600 Jacombs Road, Richmond BC, Canada V6V 3B1 | +1.604.303.2315

___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe