firezone

mirror of https://github.com/outbackdingo/firezone.git synced 2026-01-27 10:18:54 +00:00

Go to file

dependabot[bot] 02b0978c45 build(deps): bump the hilt group in /kotlin/android with 4 updates (#7922 )

Bumps the hilt group in /kotlin/android with 4 updates:
[com.google.dagger.hilt.android](https://github.com/google/dagger),
[com.google.dagger:hilt-android](https://github.com/google/dagger),
[com.google.dagger:hilt-android-compiler](https://github.com/google/dagger)
and
[com.google.dagger:hilt-android-testing](https://github.com/google/dagger).

Updates `com.google.dagger.hilt.android` from 2.54 to 2.55
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/google/dagger/releases">com.google.dagger.hilt.android's
releases</a>.</em></p>
<blockquote>
<h2>Dagger 2.55</h2>
<h1>Notable/breaking changes</h1>
<ul>
<li>Added support for injecting <code>jakarta.inject.Provider</code>.
This should be usable anywhere <code>javax.inject.Provider</code> is
usable. Note that this technically comes with a breaking change to
disallow providing <code>jakarta.inject.Provider</code> types in the
same way it is disallowed for <code>javax.inject.Provider</code>.
(caa7e178b)</li>
<li>Fixed a number of binding graph related issues.
These fixes can be enabled with,
<code>-Adagger.useBindingGraphFix=ENABLED</code>, but due to this
sometimes being a breaking change we’ve set the default behavior to
“disabled” for now. We will flip the default to “enabled” in a future
release, and eventually remove the flag altogether. Enabling this
feature can fix a number of confusing error messages. See <a
href="https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix">https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix</a>
for more details.</li>
</ul>
<h1>Bug fixes</h1>
<ul>
<li>Fixed <a
href="https://redirect.github.com/google/dagger/issues/4549">#4549</a>:
Fixed incremental processing for LazyClassKey proguard files by adding
the
originating element to the <code>writeResource</code> call.
(98a027541)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="14ad560f70"><code>14ad560</code></a>
2.55 release</li>
<li><a
href="7ca9977009"><code>7ca9977</code></a>
Add binary compatibility validator to the Gradle projects</li>
<li><a
href="4cd83cb8a6"><code>4cd83cb</code></a>
Add documentation for <code>dagger.useBindingGraphFix</code> compiler
option.</li>
<li><a
href="8b4f9b6421"><code>8b4f9b6</code></a>
Add maven publish plugin to Gradle projects.</li>
<li><a
href="9daa0ae7b1"><code>9daa0ae</code></a>
Wire resource configuration while keeping the Bazel project
structure.</li>
<li><a
href="3418609a2b"><code>3418609</code></a>
Move JDK toolchain, Kotlin language and JVM target configuration to
conventio...</li>
<li><a
href="0927b9a514"><code>0927b9a</code></a>
Add flag to control LegacyBindingGraphFactory usage.</li>
<li><a
href="1620e92d6d"><code>1620e92</code></a>
Add Github CI step and action for building with Gradle</li>
<li><a
href="c43783a4b7"><code>c43783a</code></a>
Initial setup of Gradle as a build system for Dagger</li>
<li><a
href="98a0275416"><code>98a0275</code></a>
Fix LazyClassKey proguard file issues.</li>
<li>Additional commits viewable in <a
href="https://github.com/google/dagger/compare/dagger-2.54...dagger-2.55">compare
view</a></li>
</ul>
</details>
<br />

Updates `com.google.dagger:hilt-android` from 2.54 to 2.55
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/google/dagger/releases">com.google.dagger:hilt-android's
releases</a>.</em></p>
<blockquote>
<h2>Dagger 2.55</h2>
<h1>Notable/breaking changes</h1>
<ul>
<li>Added support for injecting <code>jakarta.inject.Provider</code>.
This should be usable anywhere <code>javax.inject.Provider</code> is
usable. Note that this technically comes with a breaking change to
disallow providing <code>jakarta.inject.Provider</code> types in the
same way it is disallowed for <code>javax.inject.Provider</code>.
(caa7e178b)</li>
<li>Fixed a number of binding graph related issues.
These fixes can be enabled with,
<code>-Adagger.useBindingGraphFix=ENABLED</code>, but due to this
sometimes being a breaking change we’ve set the default behavior to
“disabled” for now. We will flip the default to “enabled” in a future
release, and eventually remove the flag altogether. Enabling this
feature can fix a number of confusing error messages. See <a
href="https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix">https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix</a>
for more details.</li>
</ul>
<h1>Bug fixes</h1>
<ul>
<li>Fixed <a
href="https://redirect.github.com/google/dagger/issues/4549">#4549</a>:
Fixed incremental processing for LazyClassKey proguard files by adding
the
originating element to the <code>writeResource</code> call.
(98a027541)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="14ad560f70"><code>14ad560</code></a>
2.55 release</li>
<li><a
href="7ca9977009"><code>7ca9977</code></a>
Add binary compatibility validator to the Gradle projects</li>
<li><a
href="4cd83cb8a6"><code>4cd83cb</code></a>
Add documentation for <code>dagger.useBindingGraphFix</code> compiler
option.</li>
<li><a
href="8b4f9b6421"><code>8b4f9b6</code></a>
Add maven publish plugin to Gradle projects.</li>
<li><a
href="9daa0ae7b1"><code>9daa0ae</code></a>
Wire resource configuration while keeping the Bazel project
structure.</li>
<li><a
href="3418609a2b"><code>3418609</code></a>
Move JDK toolchain, Kotlin language and JVM target configuration to
conventio...</li>
<li><a
href="0927b9a514"><code>0927b9a</code></a>
Add flag to control LegacyBindingGraphFactory usage.</li>
<li><a
href="1620e92d6d"><code>1620e92</code></a>
Add Github CI step and action for building with Gradle</li>
<li><a
href="c43783a4b7"><code>c43783a</code></a>
Initial setup of Gradle as a build system for Dagger</li>
<li><a
href="98a0275416"><code>98a0275</code></a>
Fix LazyClassKey proguard file issues.</li>
<li>Additional commits viewable in <a
href="https://github.com/google/dagger/compare/dagger-2.54...dagger-2.55">compare
view</a></li>
</ul>
</details>
<br />

Updates `com.google.dagger:hilt-android-compiler` from 2.54 to 2.55
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/google/dagger/releases">com.google.dagger:hilt-android-compiler's
releases</a>.</em></p>
<blockquote>
<h2>Dagger 2.55</h2>
<h1>Notable/breaking changes</h1>
<ul>
<li>Added support for injecting <code>jakarta.inject.Provider</code>.
This should be usable anywhere <code>javax.inject.Provider</code> is
usable. Note that this technically comes with a breaking change to
disallow providing <code>jakarta.inject.Provider</code> types in the
same way it is disallowed for <code>javax.inject.Provider</code>.
(caa7e178b)</li>
<li>Fixed a number of binding graph related issues.
These fixes can be enabled with,
<code>-Adagger.useBindingGraphFix=ENABLED</code>, but due to this
sometimes being a breaking change we’ve set the default behavior to
“disabled” for now. We will flip the default to “enabled” in a future
release, and eventually remove the flag altogether. Enabling this
feature can fix a number of confusing error messages. See <a
href="https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix">https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix</a>
for more details.</li>
</ul>
<h1>Bug fixes</h1>
<ul>
<li>Fixed <a
href="https://redirect.github.com/google/dagger/issues/4549">#4549</a>:
Fixed incremental processing for LazyClassKey proguard files by adding
the
originating element to the <code>writeResource</code> call.
(98a027541)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="14ad560f70"><code>14ad560</code></a>
2.55 release</li>
<li><a
href="7ca9977009"><code>7ca9977</code></a>
Add binary compatibility validator to the Gradle projects</li>
<li><a
href="4cd83cb8a6"><code>4cd83cb</code></a>
Add documentation for <code>dagger.useBindingGraphFix</code> compiler
option.</li>
<li><a
href="8b4f9b6421"><code>8b4f9b6</code></a>
Add maven publish plugin to Gradle projects.</li>
<li><a
href="9daa0ae7b1"><code>9daa0ae</code></a>
Wire resource configuration while keeping the Bazel project
structure.</li>
<li><a
href="3418609a2b"><code>3418609</code></a>
Move JDK toolchain, Kotlin language and JVM target configuration to
conventio...</li>
<li><a
href="0927b9a514"><code>0927b9a</code></a>
Add flag to control LegacyBindingGraphFactory usage.</li>
<li><a
href="1620e92d6d"><code>1620e92</code></a>
Add Github CI step and action for building with Gradle</li>
<li><a
href="c43783a4b7"><code>c43783a</code></a>
Initial setup of Gradle as a build system for Dagger</li>
<li><a
href="98a0275416"><code>98a0275</code></a>
Fix LazyClassKey proguard file issues.</li>
<li>Additional commits viewable in <a
href="https://github.com/google/dagger/compare/dagger-2.54...dagger-2.55">compare
view</a></li>
</ul>
</details>
<br />

Updates `com.google.dagger:hilt-android-testing` from 2.54 to 2.55
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/google/dagger/releases">com.google.dagger:hilt-android-testing's
releases</a>.</em></p>
<blockquote>
<h2>Dagger 2.55</h2>
<h1>Notable/breaking changes</h1>
<ul>
<li>Added support for injecting <code>jakarta.inject.Provider</code>.
This should be usable anywhere <code>javax.inject.Provider</code> is
usable. Note that this technically comes with a breaking change to
disallow providing <code>jakarta.inject.Provider</code> types in the
same way it is disallowed for <code>javax.inject.Provider</code>.
(caa7e178b)</li>
<li>Fixed a number of binding graph related issues.
These fixes can be enabled with,
<code>-Adagger.useBindingGraphFix=ENABLED</code>, but due to this
sometimes being a breaking change we’ve set the default behavior to
“disabled” for now. We will flip the default to “enabled” in a future
release, and eventually remove the flag altogether. Enabling this
feature can fix a number of confusing error messages. See <a
href="https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix">https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix</a>
for more details.</li>
</ul>
<h1>Bug fixes</h1>
<ul>
<li>Fixed <a
href="https://redirect.github.com/google/dagger/issues/4549">#4549</a>:
Fixed incremental processing for LazyClassKey proguard files by adding
the
originating element to the <code>writeResource</code> call.
(98a027541)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="14ad560f70"><code>14ad560</code></a>
2.55 release</li>
<li><a
href="7ca9977009"><code>7ca9977</code></a>
Add binary compatibility validator to the Gradle projects</li>
<li><a
href="4cd83cb8a6"><code>4cd83cb</code></a>
Add documentation for <code>dagger.useBindingGraphFix</code> compiler
option.</li>
<li><a
href="8b4f9b6421"><code>8b4f9b6</code></a>
Add maven publish plugin to Gradle projects.</li>
<li><a
href="9daa0ae7b1"><code>9daa0ae</code></a>
Wire resource configuration while keeping the Bazel project
structure.</li>
<li><a
href="3418609a2b"><code>3418609</code></a>
Move JDK toolchain, Kotlin language and JVM target configuration to
conventio...</li>
<li><a
href="0927b9a514"><code>0927b9a</code></a>
Add flag to control LegacyBindingGraphFactory usage.</li>
<li><a
href="1620e92d6d"><code>1620e92</code></a>
Add Github CI step and action for building with Gradle</li>
<li><a
href="c43783a4b7"><code>c43783a</code></a>
Initial setup of Gradle as a build system for Dagger</li>
<li><a
href="98a0275416"><code>98a0275</code></a>
Fix LazyClassKey proguard file issues.</li>
<li>Additional commits viewable in <a
href="https://github.com/google/dagger/compare/dagger-2.54...dagger-2.55">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>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

2025-01-29 01:00:52 +00:00

.github

build(deps): bump actions/setup-python from 5.3.0 to 5.4.0 (#7913 )

2025-01-29 00:57:28 +00:00

docs

refactor: use script/bump-version.sh instead of Makefile (#7907 )

2025-01-28 23:47:05 +00:00

elixir

feat(portal): Sort resources by name ASC by default (#7884 )

2025-01-27 17:38:19 +00:00

kotlin/android

build(deps): bump the hilt group in /kotlin/android with 4 updates (#7922 )

2025-01-29 01:00:52 +00:00

rust

chore: Release Android 1.4.1 (#7911 )

2025-01-29 00:29:15 +00:00

scripts

chore: Release Android 1.4.1 (#7911 )

2025-01-29 00:29:15 +00:00

swift/apple

feat(apple/macOS): Alert user if macOS 15.0.x (#7908 )

2025-01-28 20:55:40 +00:00

terraform

build(deps): Bump cyrilgdn/postgresql from 1.24.0 to 1.25.0 in /terraform/environments/production (#7777 )

2025-01-29 00:42:40 +00:00

website

build(deps): bump postcss from 8.4.49 to 8.5.1 in /website (#7923 )

2025-01-29 01:00:12 +00:00

.dockerignore

Github Actions cache on main and scope caches for all languages/runtimes (#2233 )

2023-10-04 17:29:04 -07:00

.gitattributes

chore: set same eol for all platforms (#4316 )

2024-03-25 23:05:23 +00:00

.gitignore

chore: add nix scripts (#3771 )

2024-02-27 23:56:46 +00:00

.prettierignore

style: Enforce code style across all supported languages using Prettier (#7322 )

2024-11-13 00:19:15 +00:00

.prettierrc.json

docs: update Apple docs for standalone guidance (#7589 )

2024-12-29 21:36:30 +00:00

.terraformignore

Make terraform upload less context

2023-09-28 21:46:09 -06:00

.tool-versions

chore(infra): Bump terraform to 1.10 (#7751 )

2025-01-13 23:02:12 +00:00

docker-compose.yml

fix(dev): Update tokens in local docker dev env (#7825 )

2025-01-22 05:27:01 +00:00

LICENSE

Update LICENSE to include component license clarification for subcomponents (#1806 )

2023-07-20 21:14:38 +00:00

docs/README.md

A modern alternative to legacy VPNs.

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/headless-client: Cross-platform 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/google-cloud/nat-gateway: Example Terraform configuration for deploying a cluster of Firezone Gateways behind a NAT gateway on GCP with a single egress IP.
- terraform/modules/google-cloud/apps/gateway-region-instance-group: Production-ready Terraform module for deploying regional Firezone Gateways to Google Cloud Compute using Regional Instance Groups.

Quickstart

The quickest way to get started with Firezone is to sign up for an account at https://app.firezone.dev/sign_up.

Once you've signed up, follow the instructions in the welcome email to get started.

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 our internal APIs are changing rapidly so we can't meaningfully support self-hosting Firezone in production at this time.

If you're feeling especially adventurous and want to self-host Firezone for educational or hobby purposes, follow the instructions to spin up a local development environment in CONTRIBUTING.md.

The latest published clients (on App Stores and on releases) are only guaranteed to work with the managed version of Firezone and may not work with a self-hosted portal built from this repository. This is because Apple and Google can sometimes delay updates to their app stores, and so the latest published version may not be compatible with the tip of main from this repository.

Therefore, if you're experimenting with self-hosting Firezone, you will probably want to use clients you build and distribute yourself as well.

See the READMEs in the following directories for more information on building each client:

macOS / iOS: swift/apple
Android / ChromeOS: kotlin/android
Windows / Linux: rust/gui-client

How long will 0.7 be supported until?

Firezone 0.7 is currently end-of-life and has stopped receiving updates as of January 31st, 2024. It will continue to be available indefinitely from the legacy branch of this repo under the Apache 2.0 license.

How much does it cost?

We offer flexible per-seat monthly and annual plans for the cloud-managed version of Firezone, with optional invoicing for larger organizations. See our pricing page for more details.

Those experimenting with self-hosting can use Firezone for free without feature or seat limitations, but we can't provide support for self-hosted installations at this time.

Documentation

Additional documentation on general usage, troubleshooting, and configuration can be found at https://www.firezone.dev/kb.

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.
Join our Discord Server: Join live discussions, meet other users, and chat with the Firezone team.
Open a PR: Contribute a bugfix or make a contribution to Firezone.

If you need help deploying or maintaining Firezone for your business, consider contacting our sales team to speak with a Firezone expert.

See all support options on our main support page.

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.

Languages

Elixir 57.1%

Rust 29.2%

TypeScript 5.9%

Swift 3.3%

Kotlin 1.8%

Other 2.5%