/etc/cert-proxy/hook: 25: TIMESTAMP: parameter not set #14

New issue

Open

opened 2024-05-02 09:27:38 +02:00 by mf · 0 comments

mf commented

2024-05-02 09:27:38 +02:00

Collaborator

apt policy cert-proxy-client
cert-proxy-client:
Installed: 1.18.0-1
Candidate: 1.18.0-1

The supplied default skript has the following comment:

# Environment variables with matching names are provided too.

So it should be set actually, shouldnt it? Also its purpose is not quite clear
to me. It appears to be the time when the cert-proxy-client started or some
time very soon after the start in this case:

May 02 09:11:27 host cert-proxy-client[1109741]: domain /var/lib/cert-proxy/certs/domain/privkey.pem /var/lib/cert-proxy/certs/domain/cert.pem /var/lib/cert-proxy/certs/domain/fullchain.pem /var/lib/cert-proxy/certs/domain/chain.pem 1714633887

I hoped to be able to use that timestamp to detect if the cert has changed actually (see #10), but it won't help me with that if my guesses are correct. Reporting anyway so it can be fixed in the next iteration.

> apt policy cert-proxy-client cert-proxy-client: Installed: 1.18.0-1 Candidate: 1.18.0-1 The supplied default skript has the following comment: > \# Environment variables with matching names are provided too. So it should be set actually, shouldnt it? Also its purpose is not quite clear to me. It appears to be the time when the cert-proxy-client started or some time very soon after the start in this case: > May 02 09:11:27 host cert-proxy-client[1109741]: domain /var/lib/cert-proxy/certs/domain/privkey.pem /var/lib/cert-proxy/certs/domain/cert.pem /var/lib/cert-proxy/certs/domain/fullchain.pem /var/lib/cert-proxy/certs/domain/chain.pem 1714633887 I hoped to be able to use that timestamp to detect if the cert has changed actually (see #10), but it won't help me with that if my guesses are correct. Reporting anyway so it can be fixed in the next iteration.