This means that our users around the world can now get free Let’s Encrypt certificates for domains containing characters outside of the ASCII set, which is built primarily for the English language.
Let’s Encrypt only signs end-entity certificates with RSA intermediates. We will add the ability to have end-entity certs signed by an ECDSA intermediate.
CVSROOT: /cvs
Module name: src
Changes by: florian@cvs.openbsd.org 2016/08/31 16:01:42
Added files:
usr.sbin/acme-client: ChangeLog Makefile acctproc.c base64.c
certproc.c chngproc.c dbg.c dnsproc.c
extern.h fileproc.c http.c http.h jsmn.c
jsmn.h json.c keyproc.c letskencrypt.1
main.c netproc.c revokeproc.c rsa.c rsa.h
sandbox-pledge.c util-pledge.c util.c
Log message:
Import Kristaps' letskencrypt and call it acme-client in tree.
OK to get it in deraadt@ (and probably beck@)
At least deraadt@, beck@ and otto@ are fine with the name and the
disagreements stopped.
用的是 acme-client,先前叫做 letskencrypt,以 C 開發的 ACME client。
Names/Certificate is the limit on how many domain names you can include in a single certificate. This is currently limited to 100 names, or websites, per certificate issued.
Certificates/Domain limits how many certificates can be issued that contain a single registered domain*.
This is limited to 20 certificates per domain per week. Exception: When you request a certificate with the same exact set of FQDNs as previously-issued certificate, this rate limit does not apply, but the one below does.