package/network-manager: make crypto library optional

The network-manager package currently pulls in either gnutls or libnss,
neither of which are very common and it might be the only reason why
they are present on a system.

However, most of NetworkManager works just fine without any cryptography
support, it only seems to be used in test cases and 802.1X support code.

Remove the dependency but use a library if it is present.

Note that this changes the default behavior. If network-manager was the
only package pulling in gnutls, it won't do this anymore and use the
"null" backend. Add a note about this to the manual.

Signed-off-by: Florian Larysch <fl@n621.de>
Tested-by: Marcus Hoffmann <buildroot@bubu1.eu>
Reviewed-by: Marcus Hoffmann <buildroot@bubu1.eu>
[Marcus: Change buildroot version to 2026.02 in migrating.adoc]
Signed-off-by: Marcus Hoffmann <buildroot@bubu1.eu>
This commit is contained in:
Florian Larysch
2025-05-31 16:39:22 +02:00
committed by Marcus Hoffmann
parent 130b5a124c
commit 7aa2c23f42
3 changed files with 8 additions and 2 deletions

View File

@@ -242,3 +242,8 @@ If you want to provide such libraries either:
- Serve it by adding the library to your overlay.
- Install the libraries from your project with NPM and bundle with a JavaScript
bundler.
In 2026.02, the network-manager package stopped selecting the gnutls package as
a cryptography backend automatically. Manually enable the gnutls or libnss
package if you require features that depend on a cryptography backend, such as
certificate-based authentication.