From 373636eb4f989914d9b67e7bf60f723e1c7be329 Mon Sep 17 00:00:00 2001 From: neil Date: Tue, 30 Aug 2022 15:04:30 +0800 Subject: [PATCH] restore --- ...ification-for-Gchat-channel-or-contact..md | 10 --- Change-default-CA-to-ZeroSSL.md | 61 +++++++++++++++++++ How-to-debug-acme.s.md | 1 - _Footer.md | 5 ++ notify.md | 19 ++++++ 5 files changed, 85 insertions(+), 11 deletions(-) delete mode 100644 22.Set-notification-for-Gchat-channel-or-contact..md create mode 100644 Change-default-CA-to-ZeroSSL.md delete mode 100644 How-to-debug-acme.s.md create mode 100644 _Footer.md diff --git a/22.Set-notification-for-Gchat-channel-or-contact..md b/22.Set-notification-for-Gchat-channel-or-contact..md deleted file mode 100644 index e8c355c..0000000 --- a/22.Set-notification-for-Gchat-channel-or-contact..md +++ /dev/null @@ -1,10 +0,0 @@ -First, you have determine what the "webhook" URL is for the channel or contact you'd like to notify. -In the desktop app, the "manage webhooks" option in somewhat hidden under the "heading" for the channel or contact. -Select the channel/contact and look in the middle of the page for a left arrow, the name, and a down arrow. -Click on the down arrow, select "manage webhooks" and copy the URL to the clipboard. - -Here are the step to configure Gchat notify: - -`export SAVED_GCHAT_WEBHOOK_URL='paste your webbook url here'` - -`acme.sh --set-notify --notify-hook gchat` \ No newline at end of file diff --git a/Change-default-CA-to-ZeroSSL.md b/Change-default-CA-to-ZeroSSL.md new file mode 100644 index 0000000..d4d5153 --- /dev/null +++ b/Change-default-CA-to-ZeroSSL.md @@ -0,0 +1,61 @@ + +As for now, if no `server` is provided, or you have not `--set-default-ca` yet, acme.sh uses letsencrypt as the default CA. + +https://github.com/acmesh-official/acme.sh/wiki/Server + + +Starting from `August-1st 2021`, acme.sh will release v3.0, in which the default CA will use [ZeroSSL](https://github.com/acmesh-official/acme.sh/wiki/ZeroSSL.com-CA) instead. + + +This change will only affect the newly created(issued) certs after `August-1st` (with v3.0), any pre-existing certs will still be renewed automatically against the current CA. + + +Q&A: + +1. As an existing user, what do I need to do? + + Generally, nothing needs to do. (If auto-upgrade is enabled, acme.sh can upgrade itself). + No matter acme.sh is upgraded to v3.0 or not, your existing certs will be renewed as before, against the same CA it's currently using. + +2. Will I still be able to use letsencrypt then? + + Yes, of course. You are still free to use any supported CA with providing `--server` parameter. + ``` + acme.sh --issue -d example.com --dns dns_cf --server letsencrypt + ``` +3. What if I don't like this change? I want to stick to letsencrypt? + + Yes, sure. You can `--set-default-ca` now or any time you like. Then acme.sh will always use the default ca you set: + ``` + acme.sh --set-default-ca --server letsencrypt + ``` + If you set the default CA, acme.sh will respect your choice first. It will always use this default ca in the future, no matter in `v2.*`, `v3.*` or any future `v4.*`. + + **acme.sh always respects your choice first, and will never make any changes to your files without your permissions.** + +4. My current cert is using letsencrypt, Will it be changed when renewed then? + + No, and never. Don't worry. when your cert is renewed, it will use the current CA, not the default CA. + +5. As a new user after `August-1st 2021`(v3.0), what will it look like to me? + + You can install acme.sh as normal, nothing is changed. + + You can also issue certs as normal [See how to issue a cert](https://github.com/acmesh-official/acme.sh/wiki/How-to-issue-a-cert): + ``` + acme.sh --issue -d example.com --dns dns_cf + ``` + + The cert will be issued with the default CA [ZeroSSL](https://github.com/acmesh-official/acme.sh/wiki/ZeroSSL.com-CA) + + You can also try with letsencrypt: + ``` + acme.sh --issue -d example.com --dns dns_cf --server letsencrypt + ``` + + +There is a comparison: ZeroSSL vs Let's Encrypt: + +https://zerossl.com/letsencrypt-alternative/ + + diff --git a/How-to-debug-acme.s.md b/How-to-debug-acme.s.md deleted file mode 100644 index 9cc7614..0000000 --- a/How-to-debug-acme.s.md +++ /dev/null @@ -1 +0,0 @@ -acme.sh --issue -d saverip.cf -k ec-256 --webroot /var/www/html \ No newline at end of file diff --git a/_Footer.md b/_Footer.md new file mode 100644 index 0000000..d754181 --- /dev/null +++ b/_Footer.md @@ -0,0 +1,5 @@ +__Buy me a beer, Donate to **acme.sh** if it saves your time. Your donation makes **acme.sh** better: https://donate.acme.sh/__ + +如果 acme.sh 帮你节省了时间,请考虑赏我一杯啤酒🍺, 捐助: https://donate.acme.sh/ +你的支持将会使得 **acme.sh** 越来越好. +感谢 \ No newline at end of file diff --git a/notify.md b/notify.md index d047f92..48edca7 100644 --- a/notify.md +++ b/notify.md @@ -616,3 +616,22 @@ status="$3" do-something "$subject ($status): $message" ``` + + + + +## 22. Set-notification-for-Gchat-channel-or-contact + + +First, you have determine what the "webhook" URL is for the channel or contact you'd like to notify. +In the desktop app, the "manage webhooks" option in somewhat hidden under the "heading" for the channel or contact. +Select the channel/contact and look in the middle of the page for a left arrow, the name, and a down arrow. +Click on the down arrow, select "manage webhooks" and copy the URL to the clipboard. + +Here are the step to configure Gchat notify: + +`export SAVED_GCHAT_WEBHOOK_URL='paste your webbook url here'` + +`acme.sh --set-notify --notify-hook gchat` + +