Karsten Weiss
Karsten Weiss
Or checking the (new) **storage format** of the [private key (bcrypt KDF and number of rounds)](http://www.tedunangst.com/flak/post/new-openssh-key-format-and-bcrypt-pbkdf) or the [public key (RFC 4716)](https://tools.ietf.org/html/rfc4716). Or warning about the **key age** and hinting...
I think this is basically a duplicate of the closed (FreeBSD) issue #1287.
Also, checking the bit sizes of the configured SSH **host** keys (e.g. RSA >= 2048 bit) would be another useful local check.
Would it be possible to support both the old and the new paths so that a `lustre-exporter` binary would work on both types of Lustre systems?
@mtds The `lustre_health_check` metric is probably missing in your case, doesn't it? I just ran into this issue myself when I upgrade a Lustre 2.7 system to lustre-exporter-2.0.0 and the...
Also, according to the [Lustre Support Matrix](https://wiki.whamcloud.com/display/PUB/Lustre+Support+Matrix) Lustre 2.12.x is now the LTS community release. Is the lustre_exporter ready for this version?
I've applied the .gitleaks.toml fix above to a local repository and it works. However, I wonder if this will be fixed in an official gitleaks (and OctoSec) release? Currently, gitleaks...