x-pack/packetbeat: add licensing notices and information for Npcap

[efd6]

What does this PR do?

This adds licensing notices and information for #29112.

Why is it important?

This information is a legal requirement for distributing OEM Npcap. The PR is split to ease review.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
  - [ ] I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• Confirm that the wording and locations of license information agrees with required licensing policy.

How to test this PR locally

This PR is almost entirely English semantics, comprehension is testing.

Only the final commit in this PR is new. The remainder are from #29112.

Related issues

• Depends x-pack/packetbeat: install Npcap at start-up when required #29112

Use cases

N/A

Screenshots

N/A

Logs

N/A

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[efd6]

Is this directory the right place for this or should it go in the root with additional words to note who it's relevant to — it probably already needs some of that to note that it's only relevant to Windows users. Note that currently this file doe not get placed on the target system — should it be?

[efd6]

Is this wording OK?

[efd6]

This is a place-holder file. It should probably also have a link to the canonical license file to avoid risk of errors.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-01-12T23:07:26.781+0000

• Duration: 253 min 27 sec

• Commit: a58e5e5

Test stats 🧪

Test	Results
Failed	0
Passed	47877
Skipped	4284
Total	52161

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[andrewkroh]

/test

[andrewkroh]

/package

[efd6]

While debugging the license checking issues I found that this is not run during packaging. This means that this hold won't constrain the license note customisation though it will prevent escape of the actual installer. Is this a problem and if it is where would be the best equivalent place in the packaging code path?

[andrewkroh]

I think this block is not necessary (or I don't understand something). All artifacts produced by running mage package from beats/x-pack/packetbeat directory are ELv1 (and all artifacts from beats/packetbeat are ASL2).

[efd6]

OK. This was a defensive inclusion in case beats/x-pack/packetbeat was moved to ELv2 which was something that was raised as a concern.

[efd6]

/test

[efd6]

/test

[andrewkroh]

/package

[efd6]

Abandoned in favour of #29112.