Releases: warp-tech/warpgate
Releases · warp-tech/warpgate
v0.4.1
- fixed RSA public keys not getting accepted
v0.4.0
Major updates
- This release adds experimental support for MySQL targets. Check out Adding a MySQL target on the wiki. Also see Protocol support for limitations.
- All protocols are now disabled by default. If you've used
warpgate setup
to generate your config file, no action is needed. Otherwise add an explicitenable: true
for the protocols you need.
Changes
warpgate check
now checks certificates and keys- added TLS options for HTTP targets
- added
ssh.host_key_verification
setting that allows automatically accepting (auto-accept
) or rejecting (auto-reject
) unknown host keys
v0.3.0
Major updates
Warpgate now supports exposing HTTP(S) targets through the bastion in addition to SSH targets - see https://github.com/warp-tech/warpgate/wiki/Adding-an-HTTP-target
Migration notes
- ℹ️ The Docker image now needs a configuration file provided to it through a data volume - see Getting started on Docker
- ℹ️ The
web_admin
config key has been deprecated and renamed tohttp
, and the web admin UI itself is now a part of the HTTP protocol handler.
Changes
v0.2.7
v0.2.6
v0.2.5
- e312a4b: Bump openssl-src from 111.18.0+1.1.1n to 111.20.0+1.1.1o - closes CVE-2022-1473
- 1d577e9: fixed incorrect version number
v0.2.4
v0.2.3
⚠️ Security: fixed authentication bypass whenuser.require
is not set in the config.
v0.2.2
- UI: fixed missing stats in the session view
v0.2.0
- Two-factor authentication through TOTP
- Live view for terminal sessions
- Log viewer, internal log store
- Log forwarding (for aggregation)
- SSH exec channels are now recorded as well
- Support for glibc 2.16