By Martin
I’m creating an image using Packer and during provisioning I make sure that “PasswordAuthentication” is set to no. I verified that it is by printing the config during the provisioning process.
Now when I start a droplet from the created image I don’t supply any SSH keys (because those were already added as part of the provisioning). It seems that because of this the config of my custom image is altered to allow root login via the password that is sent to me via email.
When I inspect the /etc/ssh/sshd_config file I can find an entry
PasswordAuthentication yes
Is it correct that DigitalOcean is modifying my image after creation or am I doing something wrong? This is the command I used to create the droplet. Image ID is the actual Image ID.
doctl compute droplet create test --image "31405797" --region "ams3" --size "2gb" --wait
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Accepted Answer
According to DigitalOcean support the only way to prevent any meddling with SSH configuration of custom snapshots is to supply some SSH keys.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.