Support SSH session recording configuration #650

Open
opened 2025-12-29 02:21:37 +01:00 by adam · 4 comments
Owner

Originally created by @Qup42 on GitHub (Feb 24, 2024).

Why

I would like to use the SSH session recording feature of tailscale. headscale unfortunately does not support the configuration required for SSH session recording.

Description

The scope of this is that headscale should handle the configuration options in the SSH ACL rules (recorder and enforceRecorder) that are required for SSH session recording. This includes parsing the fields from the config and setting the fields in the SSHAction response. Providing an endpoint that can receive the recordings is not in the scope of this issue.

This should be small change. I am willing to provide a PR for this feature. This issues goal is to discuss the feature before opening a PR.

Originally created by @Qup42 on GitHub (Feb 24, 2024). ## Why I would like to use the SSH session recording feature of tailscale. headscale unfortunately does not support the configuration required for SSH session recording. ## Description The scope of this is that headscale should handle the configuration options in the SSH ACL rules (`recorder` and `enforceRecorder`) that are required for SSH session recording. This includes parsing the fields from the config and setting the fields in the `SSHAction` response. Providing an endpoint that can receive the recordings is not in the scope of this issue. This should be small change. I am willing to provide a PR for this feature. This issues goal is to discuss the feature before opening a PR.
adam added the enhancementno-stale-bot labels 2025-12-29 02:21:37 +01:00
Author
Owner

@ghost commented on GitHub (Feb 26, 2024):

Have you managed to log the tsrecorder container with headscale ? When I last checked, there wasn't an option to specify a different server.

@ghost commented on GitHub (Feb 26, 2024): Have you managed to log the `tsrecorder` container with headscale ? When I last checked, there wasn't an option to specify a different server.
Author
Owner

@Qup42 commented on GitHub (Feb 26, 2024):

Have you managed to log the tsrecorder container with headscale ? When I last checked, there wasn't an option to specify a different server.

No. I am playing around with collecting the client logs and session recodings. But that this is in a repo that is private for now until it is in a usable state.

@Qup42 commented on GitHub (Feb 26, 2024): > Have you managed to log the `tsrecorder` container with headscale ? When I last checked, there wasn't an option to specify a different server. No. I am playing around with collecting the client logs and session recodings. But that this is in a repo that is private for now until it is in a usable state.
Author
Owner

@github-actions[bot] commented on GitHub (May 27, 2024):

This issue is stale because it has been open for 90 days with no activity.

@github-actions[bot] commented on GitHub (May 27, 2024): This issue is stale because it has been open for 90 days with no activity.
Author
Owner

@github-actions[bot] commented on GitHub (Jun 3, 2024):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (Jun 3, 2024): This issue was closed because it has been inactive for 14 days since being marked as stale.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#650