Before submitting
Area
apps/server
Problem or use case
Creating a new pairing token from the cli doesn't allow for limiting the scopes of that session.
Essentially I don't want my remote sessions to have terminal access for security reasons.
It is possible to create a pairing token with scopes over http, but not through the cli.
Proposed solution
Add a --scopes flag to allow uses to create pairing tokens that will have limited scopes.
Why this matters
Security with remote sessions through the t3 web app.
Smallest useful scope
A --scopes flag that takes in the allowed scopes
Alternatives considered
No response
Risks or tradeoffs
No response
Examples or references
No response
Contribution
Before submitting
Area
apps/server
Problem or use case
Creating a new pairing token from the cli doesn't allow for limiting the scopes of that session.
Essentially I don't want my remote sessions to have terminal access for security reasons.
It is possible to create a pairing token with scopes over http, but not through the cli.
Proposed solution
Add a --scopes flag to allow uses to create pairing tokens that will have limited scopes.
Why this matters
Security with remote sessions through the t3 web app.
Smallest useful scope
A --scopes flag that takes in the allowed scopes
Alternatives considered
No response
Risks or tradeoffs
No response
Examples or references
No response
Contribution