gr33nbl00d / caddy-revocation-validator Goto Github PK

Caddy fails to start and gives the following error message

caddy-caddy-1  | Error: loading initial config: loading new config: loading http app module: provision http: server srv0: setting up TLS connection policies: loading client cert verifiers: position 0: loading module 'revocation': provision tls.client_auth.revocation: end of file reached while still expecting bytes EOF

this is inside a docker container. The error message itself isn't to helpful as i don't know what is missing. I just used the minimal example from the README

Hi there,
First thanks for the great work there !
I'm looking at implementing revocation check but I'm having some issues as I'm using https://github.com/lucaslorentz/caddy-docker-proxy which generate the Caddy config automatically from docker labels.
This is done by generating a temp Caddyfile and reloading the config when containers are changed.

Without support for Caddyfile in this module I unfortunately cannot use it in my environnement.

Is there any chance Caddyfile support could be added ?
This looks quite straight forward : https://caddyserver.com/docs/extending-caddy/caddyfile

I also noticed the documentation should probably be updated, if I'm not wrong the sample config file should look like this according to latest JSON definition (validator(s) changed to verifier(s)) :

          "client_authentication": {
            "trusted_ca_certs_pem_files": [
              "./certificates/ca.pem",
            ],
            "mode": "require_and_verify",
			"verifiers": [
				{
					"verifier" : "revocation",
					"mode" : "prefer_ocsp",
					"crl_config": {
					  "work_dir": "./crlworkdir"
					},
					"ocsp_config": {
						"default_cache_duration" : "10m",
					}
				}
			]
          }

Happy to raise a PR to update it

This plugin is still in an early phase and can be considered beta. However it will get into production by end of the year on a big "unnamed customer" Till that point at least manual SW-QA tests will be performed. Automatic tests will be added in first quarter of 2022

Did this went into production? What is the future of this package?