eedf852ebe
Bumps [time](https://github.com/time-rs/time) from 0.3.36 to 0.3.37. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/time-rs/time/releases">time's releases</a>.</em></p> <blockquote> <h2>v0.3.37</h2> <p>See the <a href="https://github.com/time-rs/time/blob/main/CHANGELOG.md">changelog</a> for details.</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/time-rs/time/blob/main/CHANGELOG.md">time's changelog</a>.</em></p> <blockquote> <h2>0.3.37 [2024-12-03]</h2> <h3>Added</h3> <ul> <li><code>Time::MAX</code>, equivalent to <code>time!(23:59:59.999999999)</code></li> <li><code>[year repr:century]</code> is now supported in format descriptions. When used in conjunction with <code>[year repr:last_two]</code>, there is sufficient information to parse a date. Note that with the <code>large-date</code> feature enabled, there is an ambiguity when parsing the two back-to-back.</li> <li>Parsing of <code>strftime</code>-style format descriptions, located at <code>time::format_description::parse_strftime_borrowed</code> and <code>time::format_description::parse_strftime_owned</code></li> <li><code>time::util::refresh_tz</code> and <code>time::util::refresh_tz_unchecked</code>, which updates information obtained via the <code>TZ</code> environment variable. This is equivalent to the <code>tzset</code> syscall on Unix-like systems, with and without built-in soundness checks, respectively.</li> <li><code>Month::length</code> and <code>util::days_in_month</code>, replacing <code>util::days_in_year_month</code>.</li> <li>Expressions are permitted in <code>time::serde::format_description!</code> rather than only paths. This also drastically improves diagnostics when an invalid value is provided.</li> </ul> <h3>Changed</h3> <ul> <li> <p>Obtaining the system UTC offset on Unix-like systems should now succeed when multi-threaded. However, if the <code>TZ</code> environment variable is altered, the program will not be aware of this until <code>time::util::refresh_tz</code> or <code>time::util::refresh_tz_unchecked</code> is called. <code>refresh_tz</code> has the same soundness requirements as obtaining the system UTC offset previously did, with the requirements still being automatically enforced. <code>refresh_tz_unchecked</code> does not enforce these requirements at the expense of being <code>unsafe</code>. Most programs should not need to call either function.</p> <p>Due to this change, the <code>time::util::local_offset</code> module has been deprecated in its entirety. The <code>get_soundness</code> and <code>set_soundness</code> functions are now no-ops.</p> <p>Note that while calls <em>should</em> succeed, success is not guaranteed in any situation. Downstream users should always be prepared to handle the error case.</p> </li> </ul> <h3>Fixed</h3> <ul> <li>Floating point values are truncated, not rounded, when formatting.</li> <li>RFC3339 allows arbitrary separators between the date and time components.</li> <li>Serialization of negative <code>Duration</code>s less than one second is now correct. It previously omitted the negative sign.</li> <li><code>From<js_sys::Date> for OffsetDateTime</code> now ensures sub-millisecond values are not erroneously returned.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="d4e39b306d"><code>d4e39b3</code></a> v0.3.37 release</li> <li><a href="09439970e5"><code>0943997</code></a> Fix CI failure</li> <li><a href="8b50f04ee0"><code>8b50f04</code></a> Update lints</li> <li><a href="56f1db6dfa"><code>56f1db6</code></a> Add <code>Month::length</code>, <code>days_in_month</code></li> <li><a href="03bcfe9f28"><code>03bcfe9</code></a> Skip formatting some macros, update UI tests</li> <li><a href="4404638fe2"><code>4404638</code></a> Permit exprs in <code>serde::format_description!</code></li> <li><a href="6b43b44060"><code>6b43b44</code></a> strftime implementation</li> <li><a href="98569ffe5b"><code>98569ff</code></a> Hide deprecations from docs</li> <li><a href="febf3a10de"><code>febf3a1</code></a> Obtain local offset in multi-threaded situations</li> <li><a href="1e19827c5a"><code>1e19827</code></a> Update rstest and rstest_reuse; bump MSRV to 1.67.1 (<a href="https://redirect.github.com/time-rs/time/issues/716">#716</a>)</li> <li>Additional commits viewable in <a href="https://github.com/time-rs/time/compare/v0.3.36...v0.3.37">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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 this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Thomas Eizinger <thomas@eizinger.io>
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.
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.