4169 Commits

This Branch

This Branch

All Branches

• upgrade cf-tunnel
  neil 2021-05-29 15:17:34 +08:00
  7aa4b8247c
• Merge pull request #3525 from tresni/synology_dsm

  Synology DSM - Make certificate descriptions sed safe

  neil 2021-05-27 21:04:24 +08:00
  37339ddafc
• shellcheck cleanup

  shellcheck sees '\\' as trying to escape the trailing quote (see
  koalaman/shellcheck#1548 ).

  Brian Hartvigsen 2021-05-26 15:25:58 -06:00
  dcb51683c5
• Make certificate descriptions sed safe

  This escapes special characters used in POSIX sed to prevent mismatches.
  e.g. `SYNO_Certficiate=*.example.com` would not match a description of
  "*.example.com" and would look to match any number of double quotes (the
  last character in the sed regex prior to certificate description),
  followed by any single character, followed by "example", followed by any
  character, followed by "com".
  
  After this change, it will properly match `*.example.com` and not
  `""zexamplefcom`.
  
  Additionally we now store the certificate description as base64 encoded
  to prevent issues with single quotes.
  
  Tested on DSM 7.0-41222 (VDSM) and DSM 6.2.4-25556 (DS1515+).

  Brian Hartvigsen 2021-05-26 15:25:58 -06:00
  74a4a788b1
• add debug info
  neilpang 2021-05-25 21:57:15 +08:00
  7909273a21
• remove ngrok token
  neil 2021-05-23 23:16:04 +08:00
  40e2ebed95
• use cloudflare tunnel to test
  neil 2021-05-23 23:12:46 +08:00
  bf9b33acec
• fix format
  neil 2021-05-22 23:48:39 +08:00
  7710a33b6c
• remove ACME v1 support
  neil 2021-05-22 23:45:50 +08:00
  af3ea2d4fd
• Merge pull request #3520 from tresni/synology_dsm

  Better fix for Synology DSM setting wrong default

  neil 2021-05-20 23:05:34 +08:00
  52a3255936
• Better fix for Synology DSM setting wrong default

  As noted by @buxm, previous fix didn't work for all versions of DSM 6.
  The better fix appears to be simply not outputting the "as_default"
  parameter unless we are doing something with the default certificate.

  Brian Hartvigsen 2021-05-19 13:21:34 -06:00
  5ab9ca1c0d
• Merge pull request #3505 from willbrowningme/patch-1

  dnsapi/dns_desec.sh remove DEDYN_NAME variable

  neil 2021-05-08 21:12:56 +08:00
  461f602992
• minor
  neilpang 2021-05-08 21:09:56 +08:00
  46180435cc
• fix https://github.com/acmesh-official/acme.sh/issues/3504

  check invalid status first.

  neilpang 2021-05-07 22:02:40 +08:00
  aede5c486b
• Merge branch 'dev' of https://github.com/acmesh-official/acme.sh into dev
  neilpang 2021-05-07 21:50:22 +08:00
  fb2407386f
• fix https://github.com/acmesh-official/acme.sh/issues/3504
  neilpang 2021-05-07 21:49:47 +08:00
  aa59c46c4c
• Remove DEDYN_NAME variable from dns_desec.sh
  Will Browning 2021-05-06 16:51:43 +01:00
  c5557fc488
• Merge pull request #3350 from temoffey/deploy-gcore_cdn

  Deploy gcore_cdn fix

  neil 2021-05-05 23:48:37 +08:00
  8c14150536
• start 2.9.0
  neilpang 2021-05-04 13:32:59 +08:00
  0881cf1379
• Merge pull request #3499 from acmesh-official/dev

  sync

  neil 2021-05-03 22:20:20 +08:00
  2.8.9 d0a16b0ec0
• minor
  neil 2021-05-03 17:14:54 +08:00
  290beb90a7
• fix nginx relative path issue:

  https://github.com/acmesh-official/acme.sh/issues/1743
  https://github.com/acmesh-official/acme.sh/issues/1914

  neil 2021-05-03 17:11:02 +08:00
  0a4ef17135
• minor
  neil 2021-05-03 16:42:09 +08:00
  e0c32ce700
• fix https://github.com/acmesh-official/acme.sh/issues/3487

  suppor Ali doh and dnspod doh.

  neil 2021-05-03 16:37:13 +08:00
  e65144a105
• Merge pull request #3498 from tresni/synology_dsm

  FIX: Synology sets "default" on wrong certificate

  neil 2021-05-03 15:57:09 +08:00
  ae40445dba
• fix https://github.com/acmesh-official/acme.sh/issues/3421
  neil 2021-05-03 15:52:56 +08:00
  25a8240d12
• FIX: Synology sets "default" on wrong certificate

  For some DSM installs, it appears that setting the "default" flag to the
  string "false" actually sets it to true.  This causes Synology to set
  the last updated certificate to be the default certificate.  Using an
  empty string appears to still be accepted as a false-y value for DSMs
  where this isn't happening and corrects the behavior in the cases that
  it was.
  
  Credit to @Run-King for identifying the fix and @buxm for reporting.

  Brian Hartvigsen 2021-05-02 13:37:59 -06:00
  1a4a180e8c
• Merge branch 'dev' of https://github.com/acmesh-official/acme.sh into dev
  neilpang 2021-05-02 22:20:27 +08:00
  aea10a3b93
• upgrade freebsd
  neilpang 2021-05-02 22:20:04 +08:00
  f855862ade
• fix compatibility issue
  neil 2021-05-01 22:32:44 +08:00
  91d37c7875
• Merge pull request #3493 from goekesmi/master

  Pass content via printf string format and argument

  neil 2021-05-01 10:16:30 +08:00
  5707b93110
• arguments passed to printf are more generic

  On systems that /bin/sh is served by shells other than bash, or 
  shells that don't implement the same syntax as the bash printf builtin,
  printf -- fails to produce the output necessary for standalone operation.
  
  The test case for this was SmartOS, which uses ksh93 as its /bin/sh.
  
  This change uses the more generic method of passing a format parameter
  of a single string, and then the argument to replace it with.

  Jeff Goeke-Smith 2021-04-29 16:46:32 -04:00
  81b2d0732f
• Merge pull request #3455 from ecm75/notify_fix

  fix _exists error message if MAIL_BIN env variable is not set

  neil 2021-04-29 22:34:11 +08:00
  ec0538d251
• more simple mail.sh fix

  Reverted the original patch and changed it to the obvious simple solution provided by @Neilpang.

  Eike-Christian Müller 2021-04-29 12:53:13 +02:00
  eb0c629fad
• Merge pull request #3392 from akulumbeg/dev

  Adding DNSAPI wrapper for Websupport webhosting (Slovakia)

  neil 2021-04-19 09:46:33 +08:00
  509d3f6d30
• Merge pull request #3460 from JaZo/feature/aurora

  Add Aurora DNS API

  neil 2021-04-17 22:17:35 +08:00
  c576af7c6f
• fix format
  neilpang 2021-04-17 22:09:59 +08:00
  f3682f0e8e
• Add Aurora DNS API
  Jasper Zonneveld 2021-04-15 08:59:16 +02:00
  1c58913eeb
• fix onecom api
  neilpang 2021-04-14 22:18:01 +08:00
  cfbc294832
• Merge pull request #3479 from mjbnz/dev

  Update Telegram notification

  neil 2021-04-09 10:08:48 +08:00
  64ad8b1dac
• Update telegram.sh

  (fix shellcheck failure)

  Mike Beattie 2021-04-08 16:44:22 +12:00
  fb079f9e50
• Dump _post() call output to /dev/null

  Signed-off-by: Mike Beattie <mike@ethernal.org>

  Mike Beattie 2021-04-08 16:38:00 +12:00
  39b09f8f87
• Add debug output of $_data variable to aid diagnosis

  Signed-off-by: Mike Beattie <mike@ethernal.org>

  Mike Beattie 2021-04-08 16:37:27 +12:00
  53d26e5c5c
• Escape asterisks in notification content

  This messes with markdown parsing
  
  Signed-off-by: Mike Beattie <mike@ethernal.org>

  Mike Beattie 2021-04-08 16:36:42 +12:00
  e21f3e6c73
• Merge pull request #3478 from acmesh-official/dev

  sync

  neil 2021-04-07 22:04:08 +08:00
  edd46eb3d1
• Merge pull request #3464 from jpbede/cleverreach-deploy-sublient

  CleverReach Deploy Hook: Allow deploy to agency subaccounts

  neil 2021-04-04 19:03:33 +08:00
  e71238571a
• Make CI happy
  Jan-Philipp Benecke 2021-03-30 09:18:33 +02:00
  2867ec509e
• Make uploading cert to subaccount possible
  Jan-Philipp Benecke 2021-03-30 09:13:32 +02:00
  d853a9ebbe
• Merge pull request #3463 from c35sys/patch-1

  Use 'vault kv put' instead of 'vault write'

  neil 2021-03-29 22:27:07 +08:00
  e0d2fa98f3
• 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.
  ```

  Christophe Le Guern 2021-03-29 15:10:14 +02:00
  cc90f83463