- 24 Jan, 2023 6 commits
- 22 Jan, 2023 1 commit
-
-
neil authored
fix(dns_openstack): fix argparse error
-
- 20 Jan, 2023 2 commits
-
-
Vladislav Sharapov authored
Add equal sign to '--record' option to fix argparse error occurring when ACME token starts with '-'.
-
neil authored
Update deploy script for gcore
-
- 19 Jan, 2023 1 commit
-
-
冰雪殇璃陌梦 authored
-
- 11 Jan, 2023 2 commits
- 05 Jan, 2023 1 commit
-
-
Gavin Leo authored
https://apidocs.gcore.com/dns
-
- 26 Dec, 2022 2 commits
- 19 Dec, 2022 1 commit
-
-
neil authored
Fix assignment: _wget_out
-
- 18 Dec, 2022 1 commit
-
-
plummer86 authored
-
- 09 Dec, 2022 1 commit
-
-
Zachary Peschke authored
-
- 04 Dec, 2022 1 commit
-
-
neil authored
-
- 03 Dec, 2022 1 commit
-
-
neil authored
Refact ssh hook to use deploy config, support scp and support specifying port
-
- 29 Nov, 2022 3 commits
-
-
neil authored
Update ArvanCloud API URL - Security & CI problem
-
Arash Hatami authored
-
Arash Hatami authored
-
- 28 Nov, 2022 4 commits
-
-
Arash Hatami authored
-
Arash Hatami authored
-
Arash Hatami authored
-
neil authored
Trim trailing slash in `--home` argument's value from the get-go to avoid that subsequently created paths contain two adjacent slashes in the middle
-
- 27 Nov, 2022 3 commits
-
-
Kiril Isakov authored
Replace the BASH parameter substitution mechanism (unsupported by sh) with standard commands (supported by sh)
-
Arash Hatami authored
-
neil authored
-
- 26 Nov, 2022 2 commits
-
-
Kiril Isakov authored
# What's expected Since in `acme.sh` path strings are concatenated with a hardcoded slash in between, the left operand must never end with a trailing slash for the resulting path to be valid. Otherwise, obviously, the resulting path will have two adjacent slashes in the middle and will not be valid. # What actually happens Even though I cannot tell for each of the input params, I know this for sure for the the `--home` argument's value. If I run `acme.sh` with `--home` argument's value being a path ending in a trailing slash, ```sh acme.sh ... --debug ... --home /some/path/ ... -d somedomainna.me ... ``` I get the following (distinct) occurrencies of resulting invalid paths containing two adjacent slashes: ``` [...] Using config home:/some/path/ [...] DOMAIN_PATH='/some/path//somedomainna.me' [...] _CURL='curl --silent --dump-header /some/path//http.header -L -g ' [...] The domain key is here: /some/path//somedomainna.me/somedomainna.me.key [...] _CURL='curl --silent --dump-header /some/path//http.header -L -g -I ' [...] Your cert is in: /some/path//somedomainna.me/somedomainna.me.cer [...] Your cert key is in: /some/path//somedomainna.me/somedomainna.me.key [...] The intermediate CA cert is in: /some/path//somedomainna.me/ca.cer [...] And the full chain certs is there: /some/path//somedomainna.me/fullchain.cer ``` # Suggested fix Trim trailing slash in `--home` argument's value from the get-go.
-
Arash Hatami authored
Update API URL
-
- 23 Nov, 2022 8 commits