mirror of
https://github.com/outbackdingo/firezone.git
synced 2026-01-27 10:18:54 +00:00
9836c74ea5
Bumps the otel group in /rust with 3 updates: [tracing-stackdriver](https://github.com/NAlexPear/tracing-stackdriver), [tracing-opentelemetry](https://github.com/tokio-rs/tracing-opentelemetry) and [opentelemetry-otlp](https://github.com/open-telemetry/opentelemetry-rust). Updates `tracing-stackdriver` from 0.8.0 to 0.9.0 <details> <summary>Commits</summary> <ul> <li><a href="4a9fe0a37e"><code>4a9fe0a</code></a> ⬆ Bump version to 0.9.0</li> <li>See full diff in <a href="https://github.com/NAlexPear/tracing-stackdriver/compare/v0.8.0...v0.9.0">compare view</a></li> </ul> </details> <br /> Updates `tracing-opentelemetry` from 0.21.0 to 0.22.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tokio-rs/tracing-opentelemetry/releases">tracing-opentelemetry's releases</a>.</em></p> <blockquote> <h2>0.22.0</h2> <h3>Breaking Changes</h3> <ul> <li>Upgrade to <code>v0.21.0</code> of <code>opentelemetry</code> For list of breaking changes in OpenTelemetry, see the <a href="https://github.com/open-telemetry/opentelemetry-rust/blob/v0.21.0/opentelemetry/CHANGELOG.md">v0.21.0 changelog</a>.</li> <li>Update MSRV to require Rust 1.65+, as <code>opentelemetry</code> requires it now. (<a href="https://redirect.github.com/tokio-rs/tracing-opentelemetry/issues/68">#68</a>)</li> </ul> <h3>Fixed</h3> <ul> <li>WASM Support (<a href="https://redirect.github.com/tokio-rs/tracing-opentelemetry/issues/57">#57</a>)</li> <li>Fix potential deadlock (<a href="https://redirect.github.com/tokio-rs/tracing-opentelemetry/issues/59">#59</a>)</li> </ul> <p>Thanks to <a href="https://github.com/jesseditson"><code>@jesseditson</code></a>, <a href="https://github.com/AsmPrgmC3"><code>@AsmPrgmC3</code></a>, and <a href="https://github.com/rthomas"><code>@rthomas</code></a> for contributing to this release!</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/tokio-rs/tracing-opentelemetry/blob/v0.1.x/CHANGELOG.md">tracing-opentelemetry's changelog</a>.</em></p> <blockquote> <h1>0.22.0 (November 7, 2023)</h1> <h3>Breaking Changes</h3> <ul> <li>Upgrade to <code>v0.21.0</code> of <code>opentelemetry</code> For list of breaking changes in OpenTelemetry, see the <a href="https://github.com/open-telemetry/opentelemetry-rust/blob/v0.21.0/opentelemetry/CHANGELOG.md">v0.21.0 changelog</a>.</li> <li>Update MSRV to require Rust 1.65+, as <code>opentelemetry</code> requires it now. (<a href="https://redirect.github.com/tokio-rs/tracing-opentelemetry/issues/68">#68</a>)</li> </ul> <h3>Fixed</h3> <ul> <li>WASM Support (<a href="https://redirect.github.com/tokio-rs/tracing-opentelemetry/issues/57">#57</a>)</li> <li>Fix potential deadlock (<a href="https://redirect.github.com/tokio-rs/tracing-opentelemetry/issues/59">#59</a>)</li> </ul> <p>Thanks to <a href="https://github.com/jesseditson"><code>@jesseditson</code></a>, <a href="https://github.com/AsmPrgmC3"><code>@AsmPrgmC3</code></a>, and <a href="https://github.com/rthomas"><code>@rthomas</code></a> for contributing to this release!</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="62690b4ac9"><code>62690b4</code></a> Prepare for v0.22.0 release (<a href="https://redirect.github.com/tokio-rs/tracing-opentelemetry/issues/75">#75</a>)</li> <li><a href="2156c236db"><code>2156c23</code></a> Update otel to version 0.21 (<a href="https://redirect.github.com/tokio-rs/tracing-opentelemetry/issues/68">#68</a>)</li> <li><a href="cfc64f37b6"><code>cfc64f3</code></a> build(deps): update tracing-log requirement from 0.1.3 to 0.2.0 (<a href="https://redirect.github.com/tokio-rs/tracing-opentelemetry/issues/64">#64</a>)</li> <li><a href="70f3ed6f73"><code>70f3ed6</code></a> build(deps): update pprof requirement from 0.12.1 to 0.13.0 (<a href="https://redirect.github.com/tokio-rs/tracing-opentelemetry/issues/61">#61</a>)</li> <li><a href="bddef29233"><code>bddef29</code></a> Add support for instrumented functions which return Result (<a href="https://redirect.github.com/tokio-rs/tracing-opentelemetry/issues/28">#28</a>)</li> <li><a href="1c61ea6b56"><code>1c61ea6</code></a> Fix potential deadlock (<a href="https://redirect.github.com/tokio-rs/tracing-opentelemetry/issues/59">#59</a>)</li> <li><a href="5223a67887"><code>5223a67</code></a> Update README example Cargo.toml (<a href="https://redirect.github.com/tokio-rs/tracing-opentelemetry/issues/60">#60</a>)</li> <li><a href="a03ff2275b"><code>a03ff22</code></a> Update criterion and pprof (<a href="https://redirect.github.com/tokio-rs/tracing-opentelemetry/issues/42">#42</a>)</li> <li><a href="80ae3211db"><code>80ae321</code></a> WASM Support (<a href="https://redirect.github.com/tokio-rs/tracing-opentelemetry/issues/57">#57</a>)</li> <li>See full diff in <a href="https://github.com/tokio-rs/tracing-opentelemetry/compare/v0.21.0...v0.22.0">compare view</a></li> </ul> </details> <br /> Updates `opentelemetry-otlp` from 0.13.0 to 0.15.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/open-telemetry/opentelemetry-rust/releases">opentelemetry-otlp's releases</a>.</em></p> <blockquote> <h2>v0.15.0</h2> <h3>Added</h3> <ul> <li>More resource detectors <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/573">#573</a></li> </ul> <h3>Changed</h3> <ul> <li>Expose the Error type to allow users to set custom error handlers <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/551">#551</a></li> <li>Allow users to use different channels based on runtime in batch span processor <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/560">#560</a></li> <li>Move <code>Unit</code> into <code>metrics</code> module <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/564">#564</a></li> <li>Update trace flags to match spec <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/565">#565</a></li> </ul> <h3>Fixed</h3> <ul> <li>Fix debug loop, add notes for <code>#[tokio::test]</code> <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/552">#552</a></li> <li><code>TraceState</code> cannot insert new key-value pairs <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/567">#567</a></li> </ul> <h2>v0.14.0</h2> <h2>Added</h2> <ul> <li>Adding a dynamic dispatch to Aggregator Selector <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/497">#497</a></li> <li>Add <code>global::force_flush_tracer_provider</code> <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/512">#512</a></li> <li>Add config <code>max_attributes_per_event</code> and <code>max_attributes_per_link</code> <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/521">#521</a></li> <li>Add dropped attribute counts to events and links <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/529">#529</a></li> </ul> <h2>Changed</h2> <ul> <li>Remove unnecessary clone in <code>Key</code> type <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/491">#491</a></li> <li>Remove <code>#[must_use]</code> from <code>set_tracer_provider</code> <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/501">#501</a></li> <li>Rename remaining usage of <code>default_sampler</code> to <code>sampler</code> <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/509">#509</a></li> <li>Use current span for SDK-less context propagation <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/510">#510</a></li> <li>Always export span batch when limit reached <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/519">#519</a></li> <li>Rename message events to events <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/530">#530</a></li> <li>Update resource merge behaviour <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/537">#537</a></li> <li>Ignore links with invalid context <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/538">#538</a></li> </ul> <h2>Removed</h2> <ul> <li>Remove remote span context <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/508">#508</a></li> <li>Remove metrics quantiles <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/525">#525</a></li> </ul> <h1>Fixed</h1> <ul> <li>Allow users to use custom export kind selector <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/526">#526</a></li> </ul> <h2>Performance</h2> <ul> <li>Improve simple span processor performance <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/502">#502</a></li> <li>Local span perf improvements <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/505">#505</a></li> <li>Reduce string allocations where possible <a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/506">#506</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="d7ba1ea4f7"><code>d7ba1ea</code></a> Prepare for v0.15.0 release (<a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/572">#572</a>)</li> <li><a href="6834b64192"><code>6834b64</code></a> feat: add more resource detectors (<a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/573">#573</a>)</li> <li><a href="efbc842c11"><code>efbc842</code></a> semantic-conventions: update to v1.4.0 spec (<a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/570">#570</a>)</li> <li><a href="d70a537548"><code>d70a537</code></a> Update example and optional dependencies (<a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/568">#568</a>)</li> <li><a href="a2dd6e7779"><code>a2dd6e7</code></a> fix: TraceState cannot insert new key-value pairs. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/567">#567</a>)</li> <li><a href="dc7d81fdfa"><code>dc7d81f</code></a> Update trace flags to match spec (<a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/565">#565</a>)</li> <li><a href="635f10e15d"><code>635f10e</code></a> Move unit into metrics module (<a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/564">#564</a>)</li> <li><a href="99e51c1980"><code>99e51c1</code></a> Update lib and tracing module docs with examples (<a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/563">#563</a>)</li> <li><a href="1ca62d337e"><code>1ca62d3</code></a> feat: allow users to use different channels based on runtime in batch span pr...</li> <li><a href="fb576b0e71"><code>fb576b0</code></a> move hyper prometheus example into something runnable (<a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/562">#562</a>)</li> <li>Additional commits viewable in <a href="https://github.com/open-telemetry/opentelemetry-rust/compare/v0.13.0...v0.15.0">compare view</a></li> </ul> </details> <br /> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Thomas Eizinger <thomas@eizinger.io> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Thomas Eizinger <thomas@eizinger.io> Co-authored-by: Jamil <jamilbk@users.noreply.github.com>
A modern alternative to legacy VPNs.
Note: 🚧 The main branch is undergoing major restructuring in preparation
for the release of Firezone 1.0 🚧.
See the legacy branch if
you're looking for Firezone 0.7.
Read the 1.0 announcement for more.
Overview
Firezone is an open source platform to securely manage remote access for any-sized organization. Unlike most VPNs, Firezone takes a granular, least-privileged approach to access management with group-based policies that control access to individual applications, entire subnets, and everything in between.
Features
Firezone is:
- Fast: Built on WireGuard® to be 3-4 times faster than OpenVPN.
- Scalable: Deploy two or more gateways for automatic load balancing and failover.
- Private: Peer-to-peer, end-to-end encrypted tunnels prevent packets from routing through our infrastructure.
- Secure: Zero attack surface thanks to Firezone's holepunching tech which establishes tunnels on-the-fly at the time of access.
- Open: Our entire product is open-source, allowing anyone to audit the codebase.
- Flexible: Authenticate users via email, Google Workspace, Okta, Entra ID, or OIDC and sync users and groups automatically.
- Simple: Deploy gateways and configure access in minutes with a snappy admin UI.
Firezone is not:
- A tool for creating bi-directional mesh networks
- A full-featured router or firewall
- An IPSec or OpenVPN server
Contents of this repository
This is a monorepo containing the full Firezone product, marketing website, and product documentation, organized as follows:
- elixir: Control plane and internal Elixir libraries:
- elixir/apps/web: Admin UI
- elixir/apps/api: API for Clients, Relays and Gateways.
- rust/: Data plane and internal Rust libraries:
- rust/gateway: Gateway - Tunnel server based on WireGuard and deployed to your infrastructure.
- rust/relay: Relay - STUN/TURN server to facilitate holepunching.
- rust/linux-client: Linux CLI client.
- rust/gui-client: Cross-platform GUI client.
- swift/: macOS / iOS clients.
- kotlin/: Android / ChromeOS clients.
- website/: Marketing website and product documentation.
- terraform/: Terraform files for various example deployments.
- terraform/examples/gcp/nat_gateway: Example Terraform configurations for deploying a cluster of Firezone gateways behind a NAT gateway on GCP with single egress IP.
- terraform/modules/gateway-google-cloud-compute: Production-ready Terraform module for deploying regional Firezone gateways to Google Cloud Compute.
Quickstart
Firezone 1.x is currently accepting early access signups for closed testing. Fill out the early access form to request access and we'll be in touch!
Frequently asked questions (FAQ)
Can I self-host Firezone?
Our license won't stop you from self-hosting the entire Firezone product top to bottom, but we can't commit the resources to make this a smooth experience and therefore don't support self-hosting the control plane at this time.
If you have a business case requiring an on-prem installation of Firezone please get in touch.
If you're feeling especially adventurous and want to self-host Firezone for educational or recreational purposes, you'll want to build and distribute the clients from source to ensure they remain locked to a version compatible with your self-hosted control plane. Unfortunately, the following clients must be distributed through proprietary app stores due to restrictions imposed by Apple and Google:
- macOS
- iOS
- Android / ChromeOS
Because it's impossible to select which client version to install from a particular app store, building and distributing Firezone from source is the only to way self-host Firezone at this time.
Otherwise, if you're hobbyist or developer and are looking to spin it up locally to contribute or experiment with, see CONTRIBUTING.md.
How do I upgrade from 0.7?
Unfortunately, you can't. The good news is Firezone 1.x is much easier to setup and manage than 0.x and so you probably don't need to.
How long will 0.7 be supported until?
Firezone 0.7 is currently end-of-life and will stop receiving updates after
January 31st, 2024. It will continue to be available indefinitely from the
legacy branch of this repo under the Apache 2.0 license.
What's your pricing structure like?
Please see our pricing page at https://www.firezone.dev/pricing?utm_source=readme
Documentation
Additional documentation on general usage, troubleshooting, and configuration can be found at https://docs.firezone.dev.
Get Help
If you're looking for help installing, configuring, or using Firezone, check our community support options:
- Discussion Forums: Ask questions, report bugs, and suggest features.
- Public Slack Group: Join live discussions, meet other users, and get to know the contributors.
- Open a PR: Contribute a bugfix or make a contribution to Firezone.
Star History
Developing and Contributing
See CONTRIBUTING.md.
Security
See SECURITY.md.
License
Portions of this software are licensed as follows:
- All content residing under the "elixir/" directory of this repository, if that directory exists, is licensed under the "Elastic License 2.0" license defined in "elixir/LICENSE".
- All third party components incorporated into the Firezone Software are licensed under the original license provided by the owner of the applicable component.
- Content outside of the above mentioned directories or restrictions above is available under the "Apache 2.0 License" license as defined in "LICENSE".
WireGuard® is a registered trademark of Jason A. Donenfeld.