4106 Commits

Author SHA1 Message Date
jerrm
e1229d4c02 duckdns - fix "integer expression expected" errors (#3397)
* fix "integer expression expected" errors

* duckdns fix

* Update dns_duckdns.sh

* Update dns_duckdns.sh
2021-08-10 09:28:02 +02:00
neilpang
45a5f24d64 upgrade freebsd and solaris 2021-08-10 09:27:58 +02:00
neil
1b2b4af3cc Chain (#3408)
* fix https://github.com/acmesh-official/acme.sh/issues/3384
match the issuer to the root CA cert subject

* fix format

* fix https://github.com/acmesh-official/acme.sh/issues/3384

* remove the alt files. https://github.com/acmesh-official/acme.sh/issues/3384
2021-08-10 09:27:38 +02:00
manuel
b822da93f4 dnsapi/pdns: also normalize json response in detecting root zone 2021-08-10 09:27:38 +02:00
Gnought
6cea1cbb57 Updated --preferred-chain to issue ISRG properly
To support different openssl crl2pkcs7 help cli format
2021-08-10 09:27:38 +02:00
Vahid Fardi
4a86e71442 change name actor 2021-08-10 09:27:38 +02:00
Vahid Fardi
1d70b98941 change Author name 2021-08-10 09:27:38 +02:00
Vahid Fardi
60fcfd8ce0 change arvan api script 2021-08-10 09:27:38 +02:00
Alexander Kulumbeg
58ff7722cd Revert "Syncing with the original repo (#2)"
This reverts commit c384ed960c138f4449e79293644c4d0ec937cef1.
2021-08-10 09:27:23 +02:00
Alexander Kulumbeg
4dd333c4e1 String change 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
f5d5ce5118 Final try, leaving _hmac as before 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
dff88c16db Update dns_websupport.sh 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
4770115be6 Changing the _hmac auth back
It only works this way, apparently
2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
8363853208 added hex param to _hmac
but removed "printf "s%" ...
2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
debf06fff8 Update dns_websupport.sh 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
5d03106cd2 Changing the _hmac call into Neil's suggestion 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
bc1488ae90 Trying the original solution
_hmac sha1 "$(printf "%s" "$WS_ApiSecret" | _hex_dump | tr -d " ")" hex)
2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
c0821cb648 adding the hex parameter to _hmac call 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
1b12aebe58 Typo
Forgot a quotation mark on line 161
2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
20da70a4ab Implementing/testing Neil's suggestions 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
803aa99dec Testing double 2>/dev/null into _utc_date with sed 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
f13718b199 2>/dev/null/ to 2>/dev/null
Silly mistake with a "/" -.-
2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
70b17d1a61 Extra test - adding date -u -d
Adding this to at least partially prevent the virtually nonexistent possibility of timestamp and _utc_date() mismatch. If the normal date -u -d does not get converted (looking at you Solaris!), the poor man's method with manipulating the _utc_date() string output kicks in.
2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
103800de26 Fixing the shebang accident 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
41abe01ee1 sed workaround for "datez" 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
9948a889d9 And again 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
4495e83ee0 Yet another Solaris test 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
2745324b5a Testing datez change for Solaris 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
817d0472b6 Fix comments, error msg and time formatting 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
5b87f05cb2 "datez" var and comments 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
a263390a07 Update dns_websupport.sh 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
f6e5ab4da2 Simplified approach for the HMAC method 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
7e34de8b26 Added a forgotten ")" 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
f02dccb648 Testing HMAC 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
1d36e880b1 Update dns_websupport.sh 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
00eba97511 Update dns_websupport.sh 2021-08-10 09:25:09 +02:00
Alexander Kulumbeg
e0eeca34c7 Test original implementation by trgosk 2021-08-10 09:25:09 +02:00
Jasper Zonneveld
e508fb82f2 Add Aurora DNS API 2021-08-10 09:25:09 +02:00
neilpang
dd42da818f upgrade freebsd 2021-08-10 09:25:09 +02:00
neilpang
957c3187fa fix format 2021-08-10 09:25:09 +02:00
neilpang
fbf04e1d37 fix onecom api 2021-08-10 09:25:09 +02:00
Mike Beattie
595196cdbe Update telegram.sh
(fix shellcheck failure)
2021-08-10 09:25:09 +02:00
Mike Beattie
cfec287272 Dump _post() call output to /dev/null
Signed-off-by: Mike Beattie <mike@ethernal.org>
2021-08-10 09:25:09 +02:00
Mike Beattie
bc455f2b54 Add debug output of $_data variable to aid diagnosis
Signed-off-by: Mike Beattie <mike@ethernal.org>
2021-08-10 09:25:09 +02:00
Mike Beattie
bae08da432 Escape asterisks in notification content
This messes with markdown parsing

Signed-off-by: Mike Beattie <mike@ethernal.org>
2021-08-10 09:25:09 +02:00
Jan-Philipp Benecke
b065544fbe Make CI happy 2021-08-10 09:25:09 +02:00
Jan-Philipp Benecke
b37aa1985a Make uploading cert to subaccount possible 2021-08-10 09:25:09 +02:00
Jan-Philipp Benecke
fea67cf2ec Make uploading cert to subaccount possible 2021-08-10 09:25:09 +02:00
Christophe Le Guern
392de503cd Use 'vault kv put' instead of 'vault write'
When using vault_cli with a kv2 path, it isn't working. I have the following error:
```
WARNING! The following warnings were returned from Vault:                                                                                                                                                                                     
                                                                                                                                                                                                                                              
  * Invalid path for a versioned K/V secrets engine. See the API docs for the                                                                                                                                                                 
  appropriate API endpoints to use. If using the Vault CLI, use 'vault kv put'                                                                                                                                                                
  for this operation.                                                                                                                                                                                                                         
```
The new way to write data  is to use `vault kv put`, it is compatible with kv1 and kv2.
Ref: https://www.vaultproject.io/docs/commands#reading-and-writing-data
```
The original version of K/V used the common read and write operations. A more advanced K/V Version 2 engine was released in Vault 0.10 and introduced the kv get and kv put commands.
```
2021-08-10 09:25:09 +02:00
wout
78769ed894 Workaround for Solaris, as it does not support non-greedy regex 2021-08-10 09:25:09 +02:00