mirror of
https://github.com/gravitational/teleport
synced 2024-10-22 18:23:25 +00:00
Make milv happy
This commit is contained in:
parent
d76b753c27
commit
5a24e9f725
|
@ -1,6 +1,6 @@
|
|||
# Enhanced Session Recording
|
||||
|
||||
Teleport [standard session recordings](https://gravitational.com/teleport/docs/architecture/teleport_nodes/#session-recording) only capture what is echoed to a terminal.
|
||||
Teleport [standard session recordings](../../architecture/teleport_nodes/#session-recording) only capture what is echoed to a terminal.
|
||||
This has inherent advantages, for example because no input is captured, Teleport
|
||||
session recordings typically do not contain passwords that were entered into a terminal.
|
||||
|
||||
|
@ -31,7 +31,7 @@ well as kernel headers.
|
|||
|
||||
!!! tip
|
||||
|
||||
Our Standard Session Recording works with older Linux Kernels. View our [audit log docs](https://gravitational.com/teleport/docs/architecture/teleport_auth/#audit-log) for more details.
|
||||
Our Standard Session Recording works with older Linux Kernels. View our [audit log docs](../../architecture/teleport_auth/#audit-log) for more details.
|
||||
|
||||
|
||||
You can check your kernel version using the `uname` command. The output should look
|
||||
|
|
|
@ -42,7 +42,7 @@ Teleport OpenSSH supports:
|
|||
|
||||
## Setting up OpenSSH Recording Proxy Mode
|
||||
|
||||
The first step is install and setup Teleport, we recommend starting with our [Quickstart](quickstart.md) and [admin manual](admin_guide.md).
|
||||
The first step is install and setup Teleport, we recommend starting with our [Quickstart](quickstart.md) and [admin manual](admin-guide.md).
|
||||
|
||||
To enable session recording for `sshd` nodes, the cluster must be switched to
|
||||
["recording proxy" mode](architecture/teleport_proxy.md#recording-proxy-mode).
|
||||
|
@ -213,7 +213,7 @@ certificate authorities for each cluster individually.
|
|||
!!! tip "OpenSSH and Trusted Clusters"
|
||||
|
||||
If you use [recording proxy mode](architecture/teleport_proxy.md) and [trusted
|
||||
clusters](trusted-clusters.md), you need to set up the certificate authority from
|
||||
clusters](trustedclusters.md), you need to set up the certificate authority from
|
||||
the _root_ cluster to match **all** nodes, even those that belong to _leaf_
|
||||
clusters. For example, if your node naming scheme is `*.root.example.com`,
|
||||
`*.leaf1.example.com`, `*.leaf2.example.com`, then the
|
||||
|
|
Loading…
Reference in a new issue