neil

as a quick fix, I just removed the problematic "_exec" from that line.

merged to master. new release will be soon.

@iammeken it's closed by github when the fix is merged into master.

https://github.com/acmesh-official/acme.sh/wiki/Code-of-conduct

I checked the code carefully, there is nothing wrong at the client side. And here is the daliy test aginst the Zerossl production server: https://github.com/acmesh-official/acmetest/actions/workflows/ZeroSSL.yml It's passing every day. And...

great. I will try more once I have time.

建议新建不同的 linux user 账户来运行acme.sh, 每个账户可以使用独立的 api key. linux 下 新建用户的成本很低. 不建议直接改源码. 如果更新版本, 你该的源码就会被覆盖.

另一个方案是, 给 acme.sh 提供多个 data folder, 这样数据互相独立. ``` ~/acmedata1/ ~/acmedata2/ ~/acmedata3/ ``` 在运行的时候指定不同的 data folder. ``` acme.sh --config-home ~/acmedata1/ --issue ..... acme.sh --config-home ~/acmedata2/ --issue ..... ``` 为了能自动更新, 需要手动加 crontab...

不会删除多余的文件, 只会覆盖自己的已知的文件.

后面考虑加一个开关, 让 api key 保存在 单个域名的配置里面, 而不是全局保存. 这样也有弊端, 想法, 没有时间表.