Add package test data for kerberos

[Niraj-Kamdar]

[terriko]

Adding the "good first issue" flag on this one, so for anyone who is doing this as a first issue...

Instructions on how to add this type of test: https://github.com/inAdding the "good first issue" flag on this one, so for anyone who is doing this as a first issue...

Instructions on how to add this type of test: https://github.com/intel/cve-bin-tool/blob/master/test/README.md#adding-new-tests-signature-tests-against-real-files

You probably also want to read the rest of that readme file, particularly the bit on how to run only the new tests you added and how to run long tests (this will be a long test), which is near the top of the checker readme file: https://github.com/intel/cve-bin-tool/blob/master/test/README.md

The kerberos checker is here: https://github.com/intel/cve-bin-tool/blob/master/cve_bin_tool/checkers/kerberos.py

tel/cve-bin-tool/blob/master/test/README.md#adding-new-tests-signature-tests-against-real-files

You probably also want to read the rest of that readme file, particularly the bit on how to run only the new tests you added, which is near the top! Note that package tests are "long tests" so you'll need to enable those with the LONG_TESTS flag (again, described at the top of the file:

The kerberos checker is here: https://github.com/intel/cve-bin-tool/blob/master/cve_bin_tool/checkers/kerberos.py

[drs-11]

Hey I'll look into this!

[drs-11]

@Niraj-Kamdar I'm not sure why there are two kerberos test_data files. Is kerberos.py for the user client of kerberos and kerberos_5.py for the main libraries?

[inosmeet]

This should be fixed by #2509.

[terriko]

Yeah, I think we can close this one.