|
| 1 | +# REQUIRED |
| 2 | +# Kind can be one of: |
| 3 | +# - breaking-change: a change to previously-documented behavior |
| 4 | +# - deprecation: functionality that is being removed in a later release |
| 5 | +# - bug-fix: fixes a problem in a previous version |
| 6 | +# - enhancement: extends functionality but does not break or fix existing behavior |
| 7 | +# - feature: new functionality |
| 8 | +# - known-issue: problems that we are aware of in a given version |
| 9 | +# - security: impacts on the security of a product or a user’s deployment. |
| 10 | +# - upgrade: important information for someone upgrading from a prior version |
| 11 | +# - other: does not fit into any of the other categories |
| 12 | +kind: bug-fix |
| 13 | + |
| 14 | +# REQUIRED for all kinds |
| 15 | +# Change summary; a 80ish characters long description of the change. |
| 16 | +summary: Load the Npcap wpcap.dll lazily to avoid blocking Npcap upgrades on Windows |
| 17 | + |
| 18 | +# REQUIRED for breaking-change, deprecation, known-issue |
| 19 | +# Long description; in case the summary is not enough to describe the change |
| 20 | +# this field accommodate a description without length limits. |
| 21 | +description: > |
| 22 | + On Windows, importing gopacket/pcap loaded wpcap.dll in the package init, so |
| 23 | + every Beat that links Packetbeat's capture code held the DLL open even when it |
| 24 | + never captured traffic. This stopped Packetbeat from replacing wpcap.dll while |
| 25 | + upgrading Npcap and the install failed. The DLL is now loaded lazily, only when |
| 26 | + Packetbeat needs it. |
| 27 | +
|
| 28 | +# REQUIRED for breaking-change, deprecation, known-issue |
| 29 | +# impact: |
| 30 | + |
| 31 | +# REQUIRED for breaking-change, deprecation, known-issue |
| 32 | +# action: |
| 33 | + |
| 34 | +# REQUIRED for all kinds |
| 35 | +# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. |
| 36 | +component: packetbeat |
| 37 | + |
| 38 | +# AUTOMATED |
| 39 | +# OPTIONAL to manually add other PR URLs |
| 40 | +# PR URL: A link the PR that added the changeset. |
| 41 | +# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. |
| 42 | +# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. |
| 43 | +# Please provide it if you are adding a fragment for a different PR. |
| 44 | +# pr: https://github.com/owner/repo/1234 |
| 45 | + |
| 46 | +# AUTOMATED |
| 47 | +# OPTIONAL to manually add other issue URLs |
| 48 | +# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). |
| 49 | +# If not present is automatically filled by the tooling with the issue linked to the PR number. |
| 50 | +issue: https://github.com/elastic/elastic-agent/issues/14517 |
0 commit comments