Hi Michael, i think coming from 2 differents implementors...
Cheers On Fri, Apr 12, 2019 at 1:35 AM Michael Lum <[email protected]> wrote: > 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 ([email protected]) | *STAR* *SOLUTIONS* > <http://www.starsolutions.com/> | Principal Software Engineer > 4600 Jacombs Road, Richmond BC, Canada V6V 3B1 | +1.604.303.2315 > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <[email protected]> > Archives: https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:[email protected] > ?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
