Up to [cvs.NetBSD.org] / pkgsrc / security / defguard-proxy
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
defguard: updatd to 2.2.0 2.2.0 Multi-step configurable MFA methods - build MFA flows from ordered steps, each with the factors allowed to pass it, enforce them per location and assign different flows to selected groups. Use FIDO2 hardware key as MFA factor - add it using the Desktop Client, configure an MFA Flow with FIDO2 Security Key factor, assign it to your location and connect using the latest Desktop and Mobile Client (NFC). Configuring MFA factors in the Desktop Client - when a location requires an MFA method a user hasn't set up, the desktop client shows Configure MFA and guides them through the setup, without re-enrolling the instance. Users can also add more methods at any time. Bulk actions for Firewall module - select several rules to enable, disable, deploy or delete them at once. Split-DNS for Defguard clients - only your internal domains are resolved by the location's DNS servers through the VPN, while all other names use the device's normal DNS (check this issue for context). Handling multiple locations with DNS configuration connected simultaneously - each connected location's domains are resolved by that location's DNS servers, so users can stay connected to several locations at the same time. Ability to apply custom MTU to the client apps - set the MTU sent to the client apps per location, with group-level overrides for selected groups. Automatic WireGuard interface metric on Windows - in all traffic mode, the tunnel interface gets the highest priority to prevent traffic and DNS leaks outside the VPN. Bulk action to put enrolment token in Active Directory for the auto-provisioning process - select users and store their enrollment tokens in an Active Directory attribute in one step, ready for client auto-provisioning. Completely redesigned Mobile Client - update from Google Play, the App Store, or use the assets from the mobile release.
*: recursive bump for pcre2 10.49
*: revbump for pcre2 symbol versioning change
defguard*: updated to 2.1.0 2.1 makes the device itself part of the access decision - admins define the security criteria a machine must meet, and non-compliant endpoints simply can't establish a connection - and it ships a rebuilt Desktop Client whose tray mode gets your users onto the VPN in two clicks.
*: recursive bump for pcre2 10.48
defguard-gateway: updated to 2.0.3 2.0.3 Fix memory access problem on BSD.
defguard, defguard-gateway, defguard-proxy: updated to 2.0.2 2.0.2: SMTP OAuth configuration for Microsoft and Google Bulk user actions Synchronization of disabled Active Directory users LDAP integration improvements Synchronization of users only from specified groups in Microsoft directory synchronization Security improvements to the Forward Auth functionality Bug fixes and UX improvements
defguard defguard-proxy: updated to 2.0.1 2.0.1 Bug fixes
defguard: updated to 2.0.0 2.0.0 It’s a significant step up from version 1.x, featuring: a completely redesigned UI, a new and easy deployment approach (and component communication security), and some other major architectural changes.
defguard-proxy: updated to 1.6.3 1.6.3 This is a patch for the major 1.6 release. It includes dependency updates to resolve the following CVEs: CVE-2026-25541 CVE-2026-25727 CVE-2026-25639 CVE-2026-2391
*: recursive bump for pcre2 Running an old binary against the new pcre doesn't work: /usr/pkg/lib/libpcre2-8.so.0: version PCRE2_10.47 required by /usr/pkg/lib/libglib-2.0.so.0 not defined
defguard*: updated to 1.5.1 1.5.1 This patch for version 1.5 includes fixes for vulnerabilities identified during our latest penetration test. As a fully transparent organization, Defguard publishes a Pentesting Security Report page where you can track the status of our vulnerability fixes. 1.5.0 This is the biggest, most feature packed (and fixes) release we have ever done! We’ve introduced 11 major features! and nearly 100 bugfixes.
defguard-proxy: added version 1.4.0 This service is meant to serve as a proxy for a subset of functionalities of Defguard core which require public access. It provides a public REST API and communicates with core over gRPC.