fix: use id_rsa in SSH config instead of id_ed25519
The setup script was generating SSH config with IdentityFile ~/.ssh/id_ed25519 but Pulse generates id_rsa keys. Updated SSH config template to use id_rsa to match the actual key type generated by the monitoring system.
This commit is contained in:
parent
759a3b7d2f
commit
6acfc3f121
1 changed files with 2 additions and 2 deletions
|
|
@ -3947,7 +3947,7 @@ elif [ "$TEMP_MONITORING_AVAILABLE" = true ]; then
|
||||||
SSH_CONFIG="Host ${PROXY_JUMP_HOST}
|
SSH_CONFIG="Host ${PROXY_JUMP_HOST}
|
||||||
HostName ${PROXY_JUMP_IP}
|
HostName ${PROXY_JUMP_IP}
|
||||||
User root
|
User root
|
||||||
IdentityFile ~/.ssh/id_ed25519
|
IdentityFile ~/.ssh/id_rsa
|
||||||
StrictHostKeyChecking accept-new
|
StrictHostKeyChecking accept-new
|
||||||
"
|
"
|
||||||
|
|
||||||
|
|
@ -3958,7 +3958,7 @@ elif [ "$TEMP_MONITORING_AVAILABLE" = true ]; then
|
||||||
Host ${NODE}
|
Host ${NODE}
|
||||||
ProxyJump ${PROXY_JUMP_HOST}
|
ProxyJump ${PROXY_JUMP_HOST}
|
||||||
User root
|
User root
|
||||||
IdentityFile ~/.ssh/id_ed25519
|
IdentityFile ~/.ssh/id_rsa
|
||||||
StrictHostKeyChecking accept-new
|
StrictHostKeyChecking accept-new
|
||||||
"
|
"
|
||||||
fi
|
fi
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue