During development of kismet, kextractor-next-20200430 had several fixes that enable or improve kismet as well as improve any other tools that use kextract.
Future kextractor versions (kextractor-next-20210426, kextractor-4.18) were created by taking kextractor-next-20200430 as base. Therefore, they already have those fixes. However, kextractor-3.19 and kextractor-4.12.8 may still need these fixes. One such case is https://github.com/paulgazz/kmax/issues/161.
During development of kismet,
kextractor-next-20200430
had several fixes that enable or improve kismet as well as improve any other tools that use kextract.Here is the commit history for
kextractor-next-20200430
: https://github.com/paulgazz/kmax/commits/master/kextractors/kextractor-next-20200430 . The fixes start with https://github.com/paulgazz/kmax/commit/29f9883853a4daebe3600141eeb320898429923cFuture kextractor versions (
kextractor-next-20210426
,kextractor-4.18
) were created by takingkextractor-next-20200430
as base. Therefore, they already have those fixes. However,kextractor-3.19
andkextractor-4.12.8
may still need these fixes. One such case is https://github.com/paulgazz/kmax/issues/161.What to do Check if
kextractor-3.19
andkextractor-4.12.8
need the fixes as applied tokextractor-next-20200430
, and fix if so. The commit list is here: https://github.com/paulgazz/kmax/commits/master/kextractors/kextractor-next-20200430