On 27/10/2018 04:40, Thomas Walter wrote:
> Hey Mark,
>
> On 26.10.18 17:34, Mark Milhollan wrote:
>
>> Let's Encrypt changes little, processes can break whether they are
>> yearly, bi-yearly or monthly. Granted you'd think there would be
>> monitoring and then reasonably quick restoration.
>
> Let's Encrypt automates the whole process and in case that doesn't work
> for whatever reason it sends you reminders by mail way before the
> certificate finally expires.
>
> If the main process and the backup reminder both fail, you are doing
> something wrong ;).
>
> Regards,
> Thomas Walter
Problem with letsencrypt is their preferred and insisted " certbot " -
does not run (easily at least) on all flavours..
I gave up with it on slackware which is what my servers run, tried using
Crypt::LE and voila instant success, it was painless to use even for
(tested at least) renews, although it requires a working webserver so
come time to replace my comodo's on my MX's, will give me another
challenge :)
--
Kind Regards,
Noel Butler
This Email, including any attachments, may contain legally
privileged
information, therefore remains confidential and subject to copyright
protected under international law. You may not disseminate, discuss, or
reveal, any part, to anyone, without the authors express written
authority to do so. If you are not the intended recipient, please notify
the sender then delete all copies of this message including attachments,
immediately. Confidentiality, copyright, and legal privilege are not
waived or lost by reason of the mistaken delivery of this message. Only
PDF [1] and ODF [2] documents accepted, please do not send proprietary
formatted documents
Links:
------
[1] http://www.adobe.com/
[2] http://en.wikipedia.org/wiki/OpenDocument_______________________________________________
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
