Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support SSH session recording configuration #1793

Closed
Qup42 opened this issue Feb 24, 2024 · 4 comments · May be fixed by #1820
Closed

Support SSH session recording configuration #1793

Qup42 opened this issue Feb 24, 2024 · 4 comments · May be fixed by #1820
Labels
enhancement New feature or request stale

Comments

@Qup42
Copy link

Qup42 commented 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.

@Qup42 Qup42 added the enhancement New feature or request label Feb 24, 2024
@p1-olm
Copy link

p1-olm commented 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.

@Qup42
Copy link
Author

Qup42 commented 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.

Copy link
Contributor

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

@github-actions github-actions bot added the stale label May 27, 2024
Copy link
Contributor

github-actions bot commented Jun 3, 2024

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

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants