Deion Exporter fails to examine all certificates in a dire

Thanks for reporting. Sounds similar to <a class="issue-link js-issue-link" data-error

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

No certs picked up if one of the certificates in a directory has wrong SELinux context set about node-cert-exporter HOT 4 CLOSED

amimof commented on August 16, 2024

No certs picked up if one of the certificates in a directory has wrong SELinux context set

from node-cert-exporter.

Comments (4)

amimof commented on August 16, 2024

Thanks for reporting. Sounds similar to #42

from node-cert-exporter.

amimof commented on August 16, 2024

@barlik Have you tried v1.0.1?

from node-cert-exporter.

barlik commented on August 16, 2024

Hi, I've just tried v1.0.1 and the issue is still present.

Version: 0ee95f1
Commit: 0ee95f156d30ff3b2d7fad2a114c98ad4bab341a
Branch: HEAD
GoVersion: 1.13

Had a look at the code, the problem seems to be here:

node-cert-exporter/pkg/exporter/exporter.go

Line 26 in d25cd15

err := filepath.Walk(p, func(path string, info os.FileInfo, err error) error {

where filepath.Walk function calls lstat() on every file in a directory, but SELinux blocks lstat() calls when a file has incorrect SELinux context. This then causes Walk function to prematurely exit a couple of lines later.

err := filepath.Walk(p, func(path string, info os.FileInfo, err error) error {
...
		if err != nil {
			return err
		}
...
	})
	if err != nil {
		return nil, err
	}

BTW: v1.0.1 seems to have been built using a git hash that's no longer available.

from node-cert-exporter.

amimof commented on August 16, 2024

@barlik Yeah I discovered the same thing. Thanks for the PR. v1.0.1 should be this commit d25cd15

from node-cert-exporter.

Recommend Projects