🎉 Release of add-on Cloudflared 2.0.5
This commit is contained in:
@@ -86,10 +86,10 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
||||
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
||||
SOFTWARE.
|
||||
|
||||
[addon-cloudflared]: https://github.com/brenner-tobias/addon-cloudflared/tree/v2.0.4
|
||||
[addon-doc-cloudflared]: https://github.com/brenner-tobias/addon-cloudflared/blob/v2.0.4/README.md
|
||||
[addon-cloudflared]: https://github.com/brenner-tobias/addon-cloudflared/tree/v2.0.5
|
||||
[addon-doc-cloudflared]: https://github.com/brenner-tobias/addon-cloudflared/blob/v2.0.5/README.md
|
||||
[cloudflared-issue]: https://github.com/brenner-tobias/addon-cloudflared/issues
|
||||
[cloudflared-version-shield]: https://img.shields.io/badge/version-v2.0.4-blue.svg
|
||||
[cloudflared-version-shield]: https://img.shields.io/badge/version-v2.0.5-blue.svg
|
||||
[cloudflared-aarch64-shield]: https://img.shields.io/badge/aarch64-yes-green.svg
|
||||
[cloudflared-amd64-shield]: https://img.shields.io/badge/amd64-yes-green.svg
|
||||
[cloudflared-armhf-shield]: https://img.shields.io/badge/armhf-yes-green.svg
|
||||
|
||||
@@ -1,8 +1,9 @@
|
||||
## What’s changed
|
||||
- ℹ️ Update Cloudflared to version 2022.7.1 @github-actions (#120)
|
||||
## 📚 Documentation
|
||||
|
||||
## 🧰 Maintenance
|
||||
- Add section with workaround for revoking cert.pem @galbatoriz (#128)
|
||||
|
||||
- Add bug report form @elcajon (#117)
|
||||
- Change issue template file extension @elcajon (#118)
|
||||
- Update bug_report.yml @elcajon (#119)
|
||||
## ⬆️ Dependency updates
|
||||
|
||||
- Bump frenck/action-yamllint from 1.1 to 1.2 @dependabot (#124)
|
||||
- Bump docker/build-push-action from 3.0.0 to 3.1.0 @dependabot (#126)
|
||||
|
||||
@@ -42,6 +42,25 @@ and a manual step at the first set-up.
|
||||
[Domain Name and Cloudlfare Set-Up](#domain-name-and-cloudlfare-set-up) for details.
|
||||
1. **Decide whether to use a [local or managed tunnel][addon-remote-or-local].**
|
||||
|
||||
### Securing Access to the Cloudflare Account
|
||||
|
||||
The Add-on downloads after authentication a `cert.pem` file to authenticate
|
||||
your instance of cloudflared against your Cloudflare account.
|
||||
You can not revoke access to this file from your cloudflare account!
|
||||
The [issue](https://github.com/cloudflare/cloudflared/issues/93)
|
||||
still persists.
|
||||
|
||||
Workaround:
|
||||
|
||||
1. Create a new Cloudflare Account and invite it to your Cloudflare account
|
||||
that manages your Domain:\
|
||||
Cloudflare Dashboard -> Manage Account -> Members -> Invite Member
|
||||
1. Instead of using your primary account to authenticate the tunnel,
|
||||
use your secondary account.
|
||||
|
||||
If your `cert.pem` file is compromised, you can revoke your
|
||||
secondary account from your primary account.
|
||||
|
||||
### Initial Add-on Setup for local tunnels
|
||||
|
||||
The following instructions describe the minimum necessary steps to use this add-on:
|
||||
|
||||
@@ -42,4 +42,4 @@ schema:
|
||||
- str?
|
||||
slug: cloudflared
|
||||
url: https://github.com/brenner-tobias/addon-cloudflared/
|
||||
version: 2.0.4
|
||||
version: 2.0.5
|
||||
|
||||
Reference in New Issue
Block a user