A command line option for tsh which would suppress storage of the identity files (certificates) and only populate the SSH Agent. An error is thrown if this is requested and the Agent is not available, or the --out option is also provided. For example:
tsh login --proxy=proxy.example.com --agent-only
In order to avoid the security risk of certificates being farmed from a user's home directory and used to access a Cluster. Identity files would only remain in memory within the Agent on the local machine.
Anyone - OSS User, Pro, Enterprise
--out=/dev/null but it stopped the Agent from being populated as well. Perhaps Agent step requires the identity files on disk already?tsh status from working?Change the UX of tsh to reduce the number of flags to improve to flow here.
@xacrimon Can you implement RFD #18 to resolve this issue?
on it
@travelton raised an excellent point: we should also expose an RBAC setting to enforce that certificates can only be stored in an SSH agent and must not be written to disk.
Should we do this in a different PR and open a new issue for it?
@xacrimon Yes, let's not delay the current implementation.
Solved by #5825