Changelog History
Page 18
-
v3.2.2 Changes
🚀 This release of Teleport contains a bug fix.
🔄 Changes
- 🛠 Fixed issue with
--bind-addr
implementation. #2650
- 🛠 Fixed issue with
-
v3.2.1 Changes
🚀 This release of Teleport contains a new feature.
🔄 Changes
- ➕ Added
--bind-addr
to forcetsh
to bind to a specific port during SSO login. #2620
- ➕ Added
-
v3.2 Changes
👍 This version brings support for Amazon's managed Kubernetes offering (EKS).
🚀 Starting with this release, Teleport proxy uses the impersonation API instead of the CSR API.
-
v3.1.15
February 21, 2020 -
v3.1.14 Changes
September 17, 2019🚀 This release of Teleport contains a bug fix.
- 🛠 Fixed issue where Web UI could not connect to older nodes within a cluster. #2993
-
v3.1.13 Changes
September 11, 2019🚀 This release of Teleport contains two bug fixes.
Description
- 🛠 Fixed issue where new versions of tsh could not connect to older clusters. #2969
- 🛠 Fixed trait encoding to be more robust. #2970
Download
🚀 Download the current and previous releases of Teleport at https://gravitational.com/teleport/download.
-
v3.1.12
September 11, 2019 -
v3.1.11 Changes
September 06, 2019🚀 This release of Teleport contains a bug fix.
Description
- 🛠 Fixed issue introduced in 3.1.10 that broke session recording when using the recording proxy. #2957
Download
🚀 Download the current and previous releases of Teleport at https://gravitational.com/teleport/download.
-
v3.1.10 Changes
September 03, 2019🚀 This release of Teleport contains multiple security fixes.
Description
🚀 As part of a routine security audit of Teleport, several security vulnerabilities and miscellaneous issues were discovered in Teleport 4.0, 3.2, and 3.1. We strongly suggest upgrading to the latest release.
Details
The most serious vulnerabilities (with severity high and medium) were centered around incorrect handling of session data. If an attacker is able to gain valid x509 credentials of a Teleport node, they could use the session recording facility to read/write arbitrary files on the Auth Server or potentially corrupt recorded session data.
This vulnerability can be only exploited using credentials from a previously authenticated client, there is no known way to exploit this vulnerability outside the cluster by non-authenticated clients.
Actions
⬆️ To mitigate these issues, upgrade all nodes, proxies, and auth servers. Upgrades should follow the normal Teleport upgrade procedure: https://gravitational.com/teleport/docs/admin-guide/#upgrading-teleport.
Download
🚀 Download one of the following releases to mitigate the issue:
Enterprise 4.0.5
Enterprise 3.2.8
Enterprise 3.1.10🚀 All current and previous releases of Enterprise can be downloaded from https://dashboard.gravitational.com.