julydate / acmedeliver Goto Github PK

Currently in order to deploy multiple certificates on one machine, you'll need to copy the client file then modify the top rows in the file (to specify different certificate, key path, or to use different reload-cmd). To solve this, maybe it's better to optionally add a new command line argument -f to specify a environment file? In that way, instead of current manual modifying the file, we can simply specify the environment file and use those specified on a per execution basis.

I have a patch ready to submit but not sure if you like that to be added to the source or not, so I decided to not include that in the current pull request #7

I just got an email from Let's Encrypt regarding their update to certificate revocation status.
I'm thinking, if there's ever a need (on the client side) to parse certificate information (such as, expiration date, current revocation status) and check that everytime the script runs in scheduled tasks (cron or systemd, for example).

If it's close to expiry or revoked, the client would request certificate from the server.

Would this be necessary or might be useful?

I'll probably write another PR to address the reload command... By current design it would trigger anytime it's executed. That's not quite ideal (especially when several instances run on different parts of the same day) - Hopefully I can get that done by this weekend.

我目前是通过nginx反代访问，想增加个CF 盾保护域名，因为直接访问也会返回内容（No domain specified.）耗费服务器资源，我看到可以使用Cloudflare提供的Access服务令牌作为访问依据，但是需要增加访问链接的标头项CF-Access-Client-Id: 与 CF-Access-Client-Secret: ，想请教下该如何在client里增加访问时携带标头？这个可以作为选配给其他人选择性使用。
使用后直接访问效果图

开发文档：https://developers.cloudflare.com/cloudflare-one/identity/service-auth/service-tokens/