Bug 15857

Summary: meta-networking - chrony: recipe is configured to use NTS, but it is not activated
Product: [Build System, Metadata & Runtime] Other YP Layers Reporter: Jairo Mejia <jairo.mejia.2708>
Component: layersAssignee: Unassigned <unassigned>
Status: RESOLVED WORKSFORME QA Contact:
Severity: minor    
Priority: Undecided CC: ccasciato, poky.bs.watcher, poky.watcher, ross.burton
Version: 5.3   
Target Milestone: 0.0.0   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Jairo Mejia 2025-05-09 21:56:18 UTC
Hi all, 

Chrony since the major 4.X version supports Network Time Security (NTS) by default. However, in order to support NTS requires gnutls. If the ./configure detects gnutls, it will activate the NTS, if not, it will silently deactivate the feature.

The recipe of chrony does not have the dependency of gnutls, so the chrony implementation do not have NTS at the end. However, according to the configuration of chrony in recipe, we do want it.

Here there are two possible solutions: 

1. we aggregate the configuration parameter '--disable-nts' to explicitly inform the user of the recipe that the default behavior of the recipe is without NTS. 
2. we put gnutls as dependency in the recipe so that the ./configure enables the NTS feature.

I would prefer the second option being the NTS feature, enable by default.

Thank you, 

JM
Comment 1 Ross Burton 2025-05-16 13:39:24 UTC
Hi Jairo,

meta-networking bugs are not tracked in this bugzilla, but instead with mails to the openembedded-devel@lists.openembedded.org mailing list.

However, it looks like this has been done in git already: https://git.openembedded.org/meta-openembedded/commit/meta-networking/recipes-support/chrony/chrony_4.6.1.bb?id=0347365edcbd265166fd25b8ce00bc81f5857eaa.

If further work is needed, then sending a patch would be much appreciated.
Comment 2 Jairo Mejia 2025-05-16 16:03:27 UTC
Hi Ross,

Thank you for the answer. I checked in the scarthgap-next branch not in the master branch. You are right, this commit solve the issue.

Thank you, 

JM