Given a configuration as follows:
domain 1.2.3.4 {
alternative names { 1.2.3.4 }
...
}
this will pass acme-client -n validation
However running acme-client will always force a renewal:
acme-client: /etc/ssl/foo.crt: certificate valid: 5 days left
acme-client: /etc/ssl/foo.crt: domain list changed, forcing renewal
The renewal is forced because the 'force' flag is set to '2' at
some point during the internal checks of the data structures.
I believe there is a bug either in the config or the validation.
If this is an invalid config, it should be rejected by the parser.
Using "domain name 1.2.3.4" instead results in a working config.
FWIW I found the use of "force = 2" sprinkled in the code a wee bit
confusing, at first glance it was unclear what this represented and
why macros were not used to clearly define the different states.
Regards
Lloyd
