-
Zero Secret Leakage:
- Tokens, cookies, and secret keys are never echoed to standard output, error dumps, or logs.
- Credentials passed via flags are sanitized in process memory.
-
At-Rest Encryption:
- Stored credentials at
~/.config/rsh/config.jsonare encrypted using AES-256-GCM. - The encryption key is derived dynamically using
scryptwith a machine-bound signature and salt. - Permissions on config files are enforced to
0600(read/write only by file owner).
- Stored credentials at
-
In-Transit Protection:
- All network traffic to
https://replit.com/graphqluses TLS 1.3. - All container WebSocket connections use WSS (
wss://eval.repl.it/wsv2/...) with strict certificate validation.
- All network traffic to
-
Container Sandboxing & Isolation:
- Remote shell sessions execute within isolated Linux MicroVMs managed by Replit Container Manager (
conman). - Process privileges follow standard non-root
runnercontainer restrictions.
- Remote shell sessions execute within isolated Linux MicroVMs managed by Replit Container Manager (
- Session Cookie (
connect.sid):- Treat your
connect.sidcookie with the same confidentiality as your Replit account password. - Do not commit
.config/rsh/or.envfiles to source control.
- Treat your
- CI / CD Pipelines:
- In automated CI/CD runners (GitHub Actions, GitLab CI), supply
REPLIT_TOKENorREPLIT_CONNECT_SIDvia repository secrets.
- In automated CI/CD runners (GitHub Actions, GitLab CI), supply
- Revoking Sessions:
- Run
rsh logoutto clear credentials locally. - Log out of your browser session at
https://replit.comto invalidate the active session cookie.
- Run