[db-wg] Proposal for restricting authentication concerning use of revoked and expired GPG ID's in key-cert objects

Dear DB WG,

It came to my attention the RIPE NCC Database does not do validation of
signed updates. (Other than checking the key is allowed to sign updates
for object(s) in question)

I got the understanding from writing to DB-WG-Chairs this was a decision
made years back.

I think is less than optimal from a security perspective an signed
update (with GPG and/or X509 certs) is not validated against (1) when
the update was signed (E.g. signing was done 10 minutes ago) and (2)
that the expiration date for the keys are not validated.

Usually I will expect if I revoke a GPG-key|X509-cert. It cannot be used
any more. But the RIPE NCC Database does still allow this currently.
This is relevant in the case I ever lose a private GPG-key|X509-cert to
less than friendly 3rd-parties. And the lost private GPG-key|X509-cert
is the one used for signing updates to the database.

What I have in mind. Is the RIPE NCC Database begins verifying validity
(not revoked and/or expired) of GPG-key|X509-cert used to sign updates with.

Christoffer