Pour avoir plusieurs certificats

If a directory name is used instead of a PEM file, then all files found in
that directory will be loaded in alphabetic order unless their name ends with
'.issuer' or '.ocsp' (reserved extensions). This directive may be specified
multiple times in order to load certificates from multiple files or
directories. The certificates will be presented to clients who provide a valid
TLS Server Name Indication field matching one of their CN or alt subjects.
Wildcards are supported, where a wildcard character '' is used instead of the
first hostname component (eg: .example.org matches www.example.org but not
www.sub.example.org).

If no SNI is provided by the client or if the SSL library does not support
TLS extensions, or if the client provides an SNI hostname which does not
match any certificate, then the first loaded certificate will be presented.
This means that when loading certificates from a directory, it is highly
recommended to load the default one first as a file or to ensure that it will
always be the first one in the directory.

Yeah !

Sympa ce workflow de protection de login

via Doo

Certains paquets sont livrés avec leur .service qu'on ne veut pas forcément utiliser
Par exemple pour redis, on peut vouloir fiare tourner plusieurs redis sur la même machine (en créant nos .service dans /etc/systemd/system)

Du coup, le .service fourni de base n'est pas vraiment utile :

systemctl disable redis-server

Si on veut qu'il n'apparaisse plus du tout dans le listing systemctl :

rm /lib/systemd/system/redis-server.service
systemctl reset-failed redis-server

css/grafana.dark.min.5aa0b879.css

.histogram-chart{min-height:250px;

/me découvre les cherry-pick