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.

Sign up for GitHub

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

Jump to bottom

Disable Recorded Sessions #1263

Closed
patrobinson opened this issue Sep 6, 2017 · 0 comments
Closed

Disable Recorded Sessions #1263

patrobinson opened this issue Sep 6, 2017 · 0 comments
Labels
feature-request Used for new features in Teleport, improvements to current should be #enhancements

Comments

@patrobinson
Copy link

patrobinson commented Sep 6, 2017 •
edited
Loading

This is related to #1111. While it appears you can now restrict who can access Recorded Sessions via the UI, they are still recorded to disk. From the manual:

Teleport also records the entire stream of bytes going to/from standard input and standard output of an SSH session.

Ideally we should be able to disable not only the recording of this byte stream, but from Teleport ever receiving it. Since this may contain sensitive information I don't want Teleport to receive it at all.
@kontsevoy kontsevoy added the feature-request Used for new features in Teleport, improvements to current should be #enhancements label Sep 7, 2017
@kontsevoy kontsevoy mentioned this issue Oct 2, 2017
Closed
@russjones russjones mentioned this issue Oct 25, 2017
Merged
hatched pushed a commit that referenced this issue Feb 1, 2023
@kimlisa
CatchError and Discover related feature extensions (#1249) (#1263)
7a9339c 
* Refactor CatchError component
- add retry and providing custom fallback funcs

* Make existing discover work resusable elsewhere
- Pull out reusable files to Share/*
- Add custom timeout messages and margin top styles for Timeout
- Allow fetching/pinging for services based on type of service for PingTeleportContext
- JoinTokenContext
  - allow fetching for tokens based on type of service
  - fix a bug that uses cached token, when coming back to the flow
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature-request Used for new features in Teleport, improvements to current should be #enhancements
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kontsevoy @patrobinson