17 days ago
Request for official SSH host key fingerprints for ssh.railway.com
Hello Railway Support,
We need to complete an Enterprise security certification for a Railway staging deployment, but our internal standard requires cryptographic verification of SSH host identity before using railway ssh.
We are blocked because railway ssh connects to ssh.railway.com, but we could not find official Railway-published SSH host key fingerprints, SSHFP DNS records, documented host key rotation, or an Enterprise-safe known_hosts procedure.
Please provide Railway-authoritative confirmation for:
- The complete list of valid SSH host key fingerprints currently served by
ssh.railway.com. - The key algorithms in use, especially ED25519.
- Whether
ssh.railway.comintentionally presents multiple fingerprints due to a distributed SSH gateway. - Whether any host key rotation happened recently.
- The recommended Enterprise-safe procedure for populating
known_hosts. - Whether Railway publishes SSHFP DNS records, or plans to publish official fingerprints in Railway docs.
- The validity period or rotation policy for these host keys.
Observed fingerprints from our environment:
- ED25519 SHA256:i4DeDzyBsin0Z9pld8Otu61KGO3M2UYtvhYFaAkA/zw
-
- ED25519 SHA256:DcDYFWljprUtKBD5aFpJJjCSv7RL2QT49K492IeSH4g
-
- ED25519 SHA256:/5tyZA1jGtJWNmC4xhTYx/kQ3p0ZVzUmcUfENBnY9o8
-
- ED25519 SHA256:+S1xg92FrnHz6pY3bpkmh1OGtWQGNANXilPzlxA7B1g
The blocking error is:
REMOTE HOST IDENTIFICATION HAS CHANGED
Host key verification failed for ssh.railway.com
We cannot accept trust-on-first-use, use StrictHostKeyChecking=no, or append keys from ssh-keyscan without Railway-authoritative confirmation.
For audit purposes, we need a clear written confirmation from Railway that identifies the valid fingerprints and the recommended trust procedure.
Thank you.
2 Replies
Status changed to Awaiting Railway Response Railway • 17 days ago
17 days ago
We do not currently publish official SSH host key fingerprints, SSHFP DNS records, or a host key rotation policy for ssh.railway.com, so there is no Railway-authoritative source to point you to for populating known_hosts today.
Status changed to Awaiting User Response Railway • 17 days ago
17 days ago
I would add to this that it is rather confusing to have ssh to ssh.railway.com to intermittently fail because of host key rotation of some sort. ssh-ing multiple times within seconds of each-other randomly results in the scary ssh message:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ED25519 key sent by the remote host is
SHA256:rM3jf93EK77AQPTuZHijCI10I/Jnw0c0MyLMjkbHvMU.
Please contact your system administrator.
Status changed to Awaiting Railway Response Railway • 17 days ago
Status changed to Awaiting User Response Railway • 17 days ago
Status changed to Solved danielalmaral • 17 days ago