- 30 Mar, 2021 2 commits
-
-
Jan-Philipp Benecke authored
-
Jan-Philipp Benecke authored
-
- 29 Mar, 2021 1 commit
-
-
Christophe Le Guern authored
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. ```
-
- 26 Mar, 2021 1 commit
-
-
Jan-Philipp Benecke authored
-
- 15 Feb, 2021 1 commit
-
-
Mike Edmunds authored
* fix: unifi deploy hook also update Cloud Key nginx certs When running on a Unifi Cloud Key device, also deploy to /etc/ssl/private/cloudkey.{crt,key} and reload nginx. This makes the new cert available for the Cloud Key management app running via nginx on port 443 (as well as the port 8443 Unifi Controller app the deploy hook already supported). Fixes #3326 * Improve settings documentation comments * Improve Cloud Key pre-flight error messaging * Fix typo * Add support for UnifiOS (Cloud Key Gen2) Since UnifiOS does not use the Java keystore (like a Unifi Controller or Cloud Key Gen1 deploy), this also reworks the settings validation and error messaging somewhat. * PR review fixes * Detect unsupported Cloud Key java keystore location * Don't try to restart inactive services (and remove extra spaces from reload command) * Clean up error messages and internal variables * Change to _getdeployconf/_savedeployconf * Switch from cp to cat to preserve file permissions
-
- 13 Jan, 2021 1 commit
-
-
Mark Challoner authored
-
- 10 Dec, 2020 5 commits
-
-
-
Brian Hartvigsen authored
Also removed unused code
-
Brian Hartvigsen authored
Small changes for DSM 6: All fields (except enable_syno_token as explained below) must either be in the GET params or the POST params, you can't mix GET and POST params enable_syno_token=yes must be in both the GET and POST params. If enable_syno_token=yes is only in the POST fields, then DSM6 returns a synotoken of --------. If enable_syno_token=yes is only in the GET params, then it returns no synotoken at all. It must be in both to work. Need to use /webapi/auth.cgi instead of /webapi/entry.cgi Verified with DSM 6.2.3-25426 Update 2 and DSM 7.0-40850
-
Thijn authored
-
Brian Hartvigsen authored
This allows us to get the cookie and the token (as it appears to be only in the body in DSM 7.) HTTP_HEADERS is only guarenteed to be output with POST for both wget and curl.
-
- 07 Dec, 2020 3 commits
- 01 Dec, 2020 1 commit
-
-
Christian Burmeister authored
I have modified the following things: Originally, "/data/assets/ssl/" is always appended to the varialbe ${_mailcow_path}. Since I use acme.sh as docker container, I only want to include the mailcow-ssl directory in the acem.sh container and not the complete mailcow directory. So now it is checked if the file generate_config.sh is in the directory (then it is the mailcow root directory, see https://github.com/mailcow/mailcow-dockerized) and only then "/data/assets/ssl/" is appended, in all other cases the passed variable is taken over unchanged. Because of the RP mailcow/mailcow-dockerized#2443 I have extended the script with ECC certificates. I adapted the reboot commands as described in the mailcow manual (https://mailcow.github.io/mailcow-dockerized-docs/firststeps-ssl/#how-to-use-your-own-certificate).
-
- 28 Nov, 2020 1 commit
-
-
Moritz H authored
-
- 09 Nov, 2020 1 commit
-
-
neil authored
-
- 02 Nov, 2020 2 commits
-
-
Sergey Pashinin authored
-
Sergey Pashinin authored
-
- 28 Oct, 2020 1 commit
-
-
Jan-Philipp Benecke authored
-
- 01 Oct, 2020 1 commit
-
-
Jan-Philipp Benecke authored
-
- 28 Aug, 2020 3 commits
-
-
Jan-Philipp Benecke authored
-
Jan-Philipp Benecke authored
-
Jan-Philipp Benecke authored
-
- 23 Aug, 2020 1 commit
-
-
Sergey Pashinin authored
-
- 18 Aug, 2020 1 commit
-
-
Sergey Pashinin authored
-
- 17 Aug, 2020 1 commit
-
-
neil authored
-
- 26 Jul, 2020 1 commit
-
-
Brian Hartvigsen authored
DS218+ appears to have a slighly different DSM that sends back headers in lowercase. Reported by @BartSiwek in #2727
-
- 16 Jul, 2020 2 commits
-
-
Viktor Szépe authored
-
Andy Botting authored
-
- 15 Jul, 2020 1 commit
-
-
Andy Botting authored
This provider relies on the the python-openstackclient and python-designateclient tools be installed and working, with either password or application credentials loaded in your env.
-
- 13 Jul, 2020 1 commit
-
-
andrewheberle authored
Ensure that reload command is encoded with base64 so special characters in command do not wreck config on renewals
-
- 29 Jun, 2020 1 commit
-
-
Tony Gravagno authored
-
- 22 May, 2020 1 commit
-
-
PM Extra authored
-
- 19 May, 2020 1 commit
-
-
kref authored
Stop it from misinterpreting a following digit as part of the escape sequence
-
- 16 May, 2020 5 commits
-
-
Brian Hartvigsen authored
SYNO_Certificate gets set by _getdeployconf, so this may be an empty string but that's fine
-
Brian Hartvigsen authored
This means, by default, we will rotate the default certificate that comes with the DSM
-
Brian Hartvigsen authored
-
Brian Hartvigsen authored
-
Brian Hartvigsen authored
I'm actually not entirely sure why/how this worked with curl but not wget, but it did. The short answer is that using a GET does not result in the HTTP_HEADER file being written, instead you must pass in the http_headers param ($2) which will return the HTTP headers as a string. Luckily, the Token is in both the body and the header. We need it and the id (and smid if 2fa) cookie to proceed. So now we parrse the response for that instead of the HTTP_HEADER file. Interesting side note: wget is fine if the URL contains a \r or \n, but curl will barf on it. So we need to make sure those are stripped from the token as it will be passed in the URL later.
-