From: Wolfgang Apolinarski <wolfgang.apolinarski@googlemail.com>
To: development@lists.ipfire.org
Subject: CAs and Let's encrypt
Date: Sat, 16 Sep 2017 12:32:01 +0200 [thread overview]
Message-ID: <002701d32ed7$095184a0$1bf48de0$@googlemail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
Hi Michael,
I think Peter already discussed the advantages/disadvantages of using your own CA vs. Verisign&Co vs. Let's encrypt.
Is there a specific reason why you don't like LE? I saw also companies switching to that - and you actually do not need to use the certbot client (although you can run it without root privileges, for example by using the webroot plugin - which I am using for my own systems).
I will have a look at the Apache configuration changes soon, sorry. I'm currently quite busy with other things, but this is on my list.
Best regards,
Wolfgang
reply other threads:[~2017-09-16 10:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002701d32ed7$095184a0$1bf48de0$@googlemail.com' \
--to=wolfgang.apolinarski@googlemail.com \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox