Update elastic-agent-libs to v0.18.0

[michel-laterman]

Proposed commit message

Update elastic-agent-libs to v.0.18.0

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.

Disruptive User Impact

elastic-agent-libs v0.18.0 updates the min accepted TLS version to 1.1, and sets the default min to 1.2.

Related Issues

• Closes Remove TLS 1.x from default list of supported protocols #41595

[botelastic]

This pull request doesn't have a Team:<team> label.

[jlind23]

@mauri870 agentbeat tests are failing with the error below, do you know what can cause this?

../filebeat/fbreceiver/receiver_test.go:133:26: NewFactory().CreateLogsReceiver undefined (type receiver.Factory has no field or method CreateLogsReceiver)

[mauri870]

@mauri870 agentbeat tests are failing with the error below, do you know what can cause this?

This should be fixed by #42199, looks like it is already merged.

[andrewkroh]

@michel-laterman Have you made documentation changes related to this change? I assume the SSL docs need updates for both the supported_protocols and cipher_suites (like purging ciphers that only work for TLS 1.0 if there are any).

[michel-laterman]

Thanks @andrewkroh, I've made #42267 to update the beats docs and elastic/ingest-docs#1609 for agent/fleet-server.

I'm not aware of any cipher_suites that are disabled with the newer revisions of TLS.

[andrewkroh]

I'm not aware of any cipher_suites that are disabled with the newer revisions of TLS.

That's probably true. It's not until TLS 1.3 that the weak cipher suites were dropped. With TLS 1.2 still being supported, there's likely none to remove at this time.