2 hours ago
Hello Railway Support,
We are preparing secure PostgreSQL integration testing for our existing PCAI-Staging project, using the staging environment and Postgres service.
Our local Ubuntu/WSL2 environment can resolve ssh.railway.com and reach TCP port 22. We have also successfully registered a dedicated SSH public key with Railway.
Before establishing an SSH connection, our security requirements mandate independently verifying the server's SSH host public key.
Could you please provide:
The current authoritative SSH host public key and SHA-256 fingerprint for ssh.railway.com on port 22, including the key algorithm.
An official, independently authenticated source or verification procedure for confirming this fingerprint.
Any recommended procedure for securely pinning the verified host key for Railway CLI SSH access.
We do not need a public database endpoint, additional services, or changes to our existing PostgreSQL configuration.
Thank you.
1 Replies
2 hours ago
We don't publish a known_hosts entry, a fingerprint list, an SSHFP record, or a host CA for ssh.railway.com, so we can't provide an authoritative host key or fingerprint to verify against. We also can't confirm whether a specific fingerprint is ours.
The endpoint is served by multiple hosts, each with its own key, and those hosts change routinely without notice. The fingerprint can differ between connections, even back-to-back ones from the same machine, and a changed fingerprint is expected rather than a sign of a problem.
Because the key is not stable, pinning a single host key will break, and we don't have a recommended pinning or known_hosts procedure for this endpoint. How you handle host key trust for it is a decision for your security requirements.
Status changed to Awaiting User Response Railway • about 2 hours ago