You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we start a droplet and ssh in for the first time we are prompted to validate the host key. If the agent is installed, the host key could be exported by it so that we can use the DO API as an out of band channel to verify the host key, using a temporary UserKnownHostsFile populated with the contents of the reported host key from do-agent when executing doctl compute ssh.
Unless there is some other way of getting the sshd public key(s), then the lack of this ensures the potential for an Entity In the Middle attack.
The authenticity of host '146.190.157.111 (146.190.157.111)' can't be established.
ED25519 key fingerprint is SHA256:KYj44PidPrB3fnxnrxHBTsIUHPKwtYrL/EkKA/oSoMo.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])?
+ doctl compute droplet create --image docker-20-04 --size s-1vcpu-1gb --region sfo3 --droplet-agent=true --tag-name scitt scitt-eve
ID Name Public IPv4 Private IPv4 Public IPv6 Memory VCPUs Disk Region Image VPC UUID Status Tags Features Volumes
384269096 scitt-eve 1024 1 25 sfo3 Ubuntu Docker 23.0.6 on Ubuntu 22.04 new scitt droplet_agent
do-agent information:
N/A, new feature request, does not exist in version 3e2db3a5c8686ca0de20be6f4c30124290277213
The text was updated successfully, but these errors were encountered:
Originally reported here: digitalocean/do-agent#305
Describe the problem
When we start a droplet and ssh in for the first time we are prompted to validate the host key. If the agent is installed, the host key could be exported by it so that we can use the DO API as an out of band channel to verify the host key, using a temporary
UserKnownHostsFile
populated with the contents of the reported host key from do-agent when executingdoctl compute ssh
.Unless there is some other way of getting the sshd public key(s), then the lack of this ensures the potential for an Entity In the Middle attack.
Steps to reproduce
Expected behavior
System Information
Distribution and version:
do-agent information:
N/A, new feature request, does not exist in version 3e2db3a5c8686ca0de20be6f4c30124290277213
The text was updated successfully, but these errors were encountered: