This release of Teleport focuses on bugfixes.
- Reduced go routine usage by the forwarding proxy. #1966
- Teleport no longer sends full version in the SSH handshake. #970
- Force flag works correctly for Trusted Clusters. #1871
- Allow manual creation of Certificate Authorities. #2001
- Include Teleport username in port forwarding events. #2004
- Allow
tctl auth sign
to create user certificate with arbitrary TTL values. #1745 - Upgrade to Go 1.10.3. #2008
This release of Teleport focuses on bugfixes.
- Use ciphers, KEX, and MAC algorithms from Teleport configuration in reverse tunnel server. #1984
- Update path sanitizer it allow
@
. #1985
This release of Teleport brings new features, significant performance and usability improvements as well usual bugfixes.
During this release cycle, the Teleport source code has been audited for security vulnerabilities by Cure53 and this release (2.6.0) contains patches for the discovered problems.
- Support for DynamoDB for storing the audit log events. #1755
- Support for Amazon S3 for storing the recorded SSH sessions. #1755
- Support for rotating certificate authorities (CA rotation). [#1899] (gravitational#1899)
- Integration with Linux PAM (pluggable authentication modules) subsystem. #742 and #1766
- The new CLI command
tsh status
shows users which Teleport clusters they are authenticated with. #1628
Additionally, Teleport 2.6.0 has been submitted to the AWS marketplace. Soon AWS users will be able to create properly configured, secure and highly available Teleport clusters with ease.
-
Role templates (depreciated in Teleport 2.3) were fully removed. We recommend migrating to role variables which are documented here
-
Resource names (like roles, connectors, trusted clusters) can no longer contain unicode or other special characters. Update the names of all user created resources to only include characters, hyphens, and dots.
-
advertise_ip
has been deprecated and replaced withpublic_addr
setting. See #1803 The existing configuration files will still work, but we advise Teleport administrators to update it to reflect the new format. -
Teleport no longer uses
boltdb
back-end for storing cluster state by default. The new default is calleddir
and it uses simple JSON files stored in/var/lib/teleport/backend
. This change applies to brand new Teleport installations, the existing clusters will continue to useboltdb
. -
The default set of enabled cryptographic primitives has been updated to reflect the latest state of SSH and TLS security. #1856.
The list of most visible bug fixes in this release:
tsh
now properly handles Ctrl+C #1882- High CPU utilization on ARM platforms during daemon start-up. #1886
- Terminal window size can get out of sync on AWS. #1874
- Some CLI commands print errors twice. #1889
- SSH session playback can be interrupted for long sessions. #1774
- Processing
HUP
UNIX signal is unreliable whenteleport
daemon runs undersystemd
. #1844
You can see the full list of 2.6.0 changes here.
Follow the recommended upgrade procedure to upgrade to this version.
This release of Teleport focuses on bugfixes.
- Allow creation of users from
tctl create
. #1949
This release of Teleport focuses on bugfixes.
- Improvements to Teleport HUP signal handling for more reliable reload. #1844
- Restore output format of
tctl nodes add --format=json
. #1846
This release of Teleport focuses on bugfixes.
- Allow creation of multiple sessions per connection (fixes Ansible issues with the recording proxy). #1811
This release of Teleport focuses on bugfixes.
- Only reset SIGINT handler if it has not been set to ignore. #1814
- Improvement of user-visible errors. #1798 #1779
This release of Teleport focuses on bugfixes.
- Fix logging, collect status of forked processes. #1785 #1776
- Turn off proxy support when no-tls is used. #1800
- Correct the signup URL. #1777
- Fix GitHub team pagination issues. #1734
- Increase global dial timeout to 30 seconds. #1760
- Reuse existing singing key. #1713
- Don't panic on channel failures. #1808
This release of Teleport includes bug fixes and regression fixes.
- Run session migration in the background. #1784
- Include node name in regenerated host certificates. #1786
This release of Teleport fixes a regression in Teleport binaries.
- Binaries for macOS have been rebuilt to resolve "certificate signed by a unknown authority" issue.
This is a major release of Teleport. Its goal is to make cloud-native deployments easier. Numerous AWS users have contributed feedback to this release, which includes:
-
Auth servers in highly available (HA) configuration can share the same
/var/lib/teleport
data directory when it's hosted on NFS (or AWS EFS). #1351 -
There is now an AWS reference deployment in
examples/aws
directory. It uses Terraform and demonstrates how to deploy large Teleport clusters on AWS using best practices like auto-scaling groups, security groups, secrets management, load balancers, etc. -
The Teleport daemon now implements built-in connection draining which allows zero-downtime upgrades. See documentation.
-
Dynamic join tokens for new nodes can now be explicitly set via
tctl node add --token
. This allows Teleport admins to use an external mechanism for generating cluster invitation tokens. #1615 -
Teleport now correctly manages certificates for accessing proxies behind a load balancer with the same domain name. The new configuration parameter
public_addr
must be used for this. #1174.
-
Switching to a new TLS-based auth server API improves performance of large clusters. #1528
-
Session recordings are now compressed by default using gzip. This reduces storage requirements by up to 80% in our real-world tests. #1579
-
More user-friendly authentication errors in Teleport audit log helps Teleport admins troubleshoot configuration errors when integrating with SAML/OIDC providers. #1554, #1553, #1599
-
tsh
client will now report if a server's API is no longer compatible.
-
tsh logout
will now correctly log out from all active Teleport sessions. This is useful for users who're connected to multiple Teleport clusters at the same time. #1541 -
When parsing YAML, Teleport now supports
--
list item separator to create multiple resources with a singletctl create
command. #1663 -
Fixed a panic in the Web UI backend #1558
Certain components of Teleport behave differently in version 2.5. It is important to note that these changes are not breaking Teleport functionality. They improve Teleport behavior on large clusters deployed on highly dynamic cloud environments such as AWS. This includes:
- Session list in the Web UI is now limited to 1,000 sessions.
- The audit log and recorded session storage has been moved from
/var/lib/teleport/log
to/var/lib/teleport/log/<auth-server-id>
. This is related to #1351 described above. - When connecting a trusted cluster users can no longer pick an arbitrary name for them.
Their own (local) names will be used, i.e. the
cluster_name
setting now defines how the cluster is seen from the outside. #1543
This release of Teleport contains a bugfix.
- Only reset SIGINT handler if it has not been set to ignore. #1814
This release of Teleport focuses on bugfixes.
This release of Teleport fixes a regression in Teleport binaries.
- Binaries for macOS have been rebuilt to resolve "certificate signed by a unknown authority" issue.
This release of Teleport focuses on bugfixes.
- Resolved
tsh logout
regression. #1541 - Binaries for supported platforms all built with Go 1.9.2.
This release of Teleport focuses on bugfixes.
- Resolved "access denied" regression in Trusted Clusters. #1733
- Key written with wrong username to
~/.tsh
. #1749 - Resolved Trusted Clusters toggling regression. #1751
This release of Teleport focuses on bugfixes.
- Wait for copy to complete before propagating exit-status. #1646
- Don't discard initial bytes in HTTP CONNECT tunnel. #1659
- Pass caching key generator to services and use cache in recording proxy. #1639
- Only display "Change Password" in UI for local users. #1669
- Update Singup URL. #1643
- Improved Teleport version reporting. #1538
- Fixed regressions in terminal size handling and Trusted Clusters introduced in 2.4.1. #1674 #1692
This release is focused on fixing a few regressions in Teleport as well as adding a new feature.
- Exposed the
--compat
flag to Web UI users. #1542
- Wrap lines correctly on initial login. #1087
- Accept port numbers larger than
32767
: #1576 - Don't show the
Join
button when using the recording proxy. #1421 - Don't double record sessions when using the recording proxy and Teleport nodes. #1582
- Fixed regressions in
tsh login
andtsh logout
. #1611 #1541
This release adds two major new features and a few improvements and bugfixes.
- New Commercial Teleport Editions: "Pro" and "Business" allow users to purchase a Teleport subscription without signing contracts.
- Teleport now supports SSH session recording even for nodes running OpenSSH #1327 This feature is called "recording proxy mode".
- Users of open source edition of Teleport can now authenticate against Github #1445
- The Web UI now supports persistent URLs to Teleport nodes which can be integrated into 3rd party web apps. #1511
- Session recording can now be turned off #1430
- Teleport client
tsh
no longer supports being an SSH agent. We recommend using build-in SSH agents for MacOS and Linux, likessh-agent
fromopenssh-client
package.
There have been numerous small usability and performance improvements, but some notable fixed bugs are listed below:
- Resource (file descriptor) leak #1433
- Correct handling of the terminal type #1402
- Crash on startup #1395
This release is focused on fixing a few regressions in configuration and UI/UX.
- Updated documentation to accurately reflect 2.3 changes
- Web UI can use introspection so users can skip explicitly specifying SSH port #1410
- Fixed issue of 2FA users getting prematurely locked out #1347
- UI (regression) when invite link is expired, nothing is shown to the user #1400
- OIDC regression with some providers #1371
- Legacy configuration for trusted clusters regression: #1381
- Dynamic tokens for adding nodes: "access denied" #1348
This release focus was to increase Teleport user experience in the following areas:
- Easier configuration via
tctl
resource commands. - Improved documentation, with expanded 'examples' directory.
- Improved CLI interface.
- Web UI improvements.
- Web UI: users can connect to OpenSSH servers using the Web UI.
- Web UI now supports arbitrarty SSH logins, in addition to role-defined ones, for better compatibility with OpenSSH.
- CLI: trusted clusters can now be managed on the fly without having to edit Teleport configuration. #1137
- CLI:
tsh login
supports exporting a user identity into a file to be used later with OpenSSH. tsh agent
command has been deprecated: users are expected to use native SSH Agents on their platforms.
- More granular RBAC rules #1092
- Role definitions now support templates. #1120
- Authentication: Teleport now supports multilpe OIDC/SAML endpoints.
- Configuration: local authentication is always enabled as a fallback if a SAML/OIDC endpoints go offline.
- Configuration: SAML/OIDC endpoints can be created on the fly using
tctl
and without having to edit configuration file or restart Teleport. - Web UI: it is now easier to turn a trusted cluster on/off #1199.
- Proper handling of
ENV_SUPATH
from login.defs #1004 - Reverse tunnels would periodically lose connectivity. #1156
- tsh now stores user identities in a format compatible with OpenSSH. 1171.
- Updated YAML parsing library. #1226
- Fixed issue with SSH dial potentially hanging indefinitely. #1153
- Fixed issue where node did not have correct permissions. #1151
- Fixed issue with remote tunnel timeouts. #1140.
- Fixed issue with Trusted Clusters where a clusters could lose its signing keys. #1050.
- Fixed SAML signing certificate export in Enterprise. #1109.
- Fixed an issue where in certain situations
tctl ls
would not work. #1102.
- Added
--compat=oldssh
to bothtsh
andtctl
that can be used to request certificates in the legacy format (no roles in extensions). #1083
- Fixed multiple regressions when using SAML with dynamic roles. #1080
- HTTP CONNECT tunneling for Trusted Clusters. #860
- Long lived certificates and identity export which can be used for automation. #1033
- New terminal for Web UI. #933
- Read user environment files. #1014
- Improvements to Auth Server resiliency and availability. #1071
- Server side configuration of support ciphers, key exchange (KEX) algorithms, and MAC algorithms. #1062
- Renaming
tsh
tossh
or making a symlinktsh -> ssh
removes the need to typetsh ssh
, making it compatible with familiarssh user@host
. #929
- SAML 2.0. #1070
- Role mapping for Trusted Clusters. #983
- ACR parsing for OIDC identity providers. #901
- Improvements to OpenSSH interoperability.
tsh
profile is now always read. #1047- Correct signal handling when Teleport is launched using sysvinit. #981
- Role templates now automatically fill out default values when omitted. #912
- Fixed regression in TLP-01-009.
Teleport 2.0.5 contains a variety of security fixes. We strongly encourage anyone running Teleport 2.0.0 and above to upgrade to 2.0.5.
The most pressing issues (a phishing attack which can potentially be used to extract plaintext credentials and an attack where an already authenticated user can escalate privileges) can be resolved by upgrading the web proxy. However, however all nodes need to be upgraded to mitigate all vulnerabilities.
- Patch for TLP-01-001 and TLP-01-003: Check redirect.
- Patch for TLP-01-004: Always check is namespace is valid.
- Patch for TLP-01-005: Check user principal when joining session.
- Patch for TLP-01-006 and TLP-01-007: Validate Session ID.
- Patch for TLP-01-008: Use a fake hash for password authentication if user does not exist.
- Patch for TLP-01-009: Command injection in scp.
- Roles created the the Web UI now have
node
resource. #949
- Execute commands using user's shell. #943
- Allow users to read their own roles. #941
- Fix User CA import. #919
- Role template defaults. #916
- Skip UserInfo if not provided. #915
- Agent socket had wrong permissions. #936
- Introduced Dynamic Roles. #897
This is a major new release of Teleport.
- Native support for DynamoDB back-end for storing cluster state.
- It is now possible to turn off 2nd factor authentication.
- 2nd factor now uses TOTP. #522
- New and easy to use framework for implementing secret storage plug-ins.
- Audit log format has been finalized and documented.
- Experimental simple file-based secret storage back-end.
- SSH agent forwarding.
- Friendlier CLI error messages.
tsh login
is now compatible with SSH agents.
- Role-based access control (RBAC)
- Dynamic configuration: ability to manage roles and trusted clusters at runtime.
Full list of Github issues: https://github.com/gravitational/teleport/milestone/8
v1.3.2 is a maintenance release which fixes a Web UI issue when in some cases static web assets like custom fonts would not load properly.
- Issue #687 - broken web assets on some browsers.
v1.3.1 is a maintenance release which fixes a few issues found in 1.3
- Teleport session recorder can skip characters.
- U2F was enabled by default in "demo mode" if teleport.yaml file was missing.
- U2F documentation has been improved
This release includes several major new features and it's recommended for production use.
- Support for hardware U2F keys for 2nd factor authentication.
- CLI client profiles: tsh can now remember its --proxy setting.
- tctl auth sign command to allow administrators to generate user session keys
- Web UI is now served directly from the executable. There is no more need for web
assets in
/usr/local/share/teleport
- Multiple auth servers in config doesn't work if the last on is not reachable. #593
tsh scp -r
does not handle directory upload properly #606
This is a maintenance release and it's a drop-in replacement for previous versions.
- Usability bugfixes as can be seen here
- Updated documentation
- Added examples directory with sample configuration and systemd unit file.
This is a maintenance release meant to be a drop-in upgrade of previous versions.
- User experience improvements: nicer error messages
- Better compatibility with ssh command: -t flag can be used to force allocation of TTY
This release was recommended for production with one reservation: time-limited certificates did not work correctly in this release due to #529
- Improvements in performance and usability of the Web UI
- Smaller binary sizes thanks to Golang v1.7
- Wrong url to register new users. #497
- Logged in users inherit Teleport supplemental groups bug security. #507
- Joining a session running on a trusted cluster does not work. #504
This release only includes the addition of the ability to specify non-standard HTTPS port for Teleport proxy for tsh --proxy flag.
This release only includes one major bugfix #486 plus minor changes not exposed to OSS Teleport users.
- Guessing
advertise_ip
chooses IPv6 address space. #486
The first official release of Teleport!