Multiple keys are added to authorized_keys without line breaks

[asostechnix]

I am running atmoz/sftp:alpine in Azure Container Instances.

I have two RSA public keys for the same user, which are mounted as a secret volume into /home/username/.ssh/keys

The file /home/username/.ssh/authorized_keys does contain both keys once the container is running but without a line break between them, which causes key auth to fail.

I have tried adding a single line break to the end of the secrets in the volume definition but it didn't make a difference.

[TobiTh]

We have the same issue. A manual insertion of a line break in the /home/username/.ssh/authorized_keys file between the keys has solved the login issue.

[jalleyne]

Same issue here, building a Helm chart using this base image and running into the issue. Helm strips out any whitespaces so its even more difficult to add them in. Confirming this is an issue so I will look at the code to submit a PR if I can make the time today.

[jalleyne]

I have a working fix that forces a new line with this proposed change. Does anyone see any concerns with this update?

Suggested fix:

echo -e "$(cat "$publickey")" >> "$userKeysAllowedFileTmp"

Existing read and append code:

sftp/files/create-sftp-user

Lines 89 to 91 in 302390e

	for publickey in "$userKeysQueuedDir"/*; do
	cat "$publickey" >> "$userKeysAllowedFileTmp"
	done

[aiac]

@jalleyne i needed to build the image from repo because there is no ARM image in Docker hub. I can confirm that your change fixed the key files error that was causing container to fail on init. Thank you. It works with the latest alpine

[tmakin]

For anyone else hitting this when deploying via config map here is a hack that allows multiple public keys to be supplied.

apiVersion: v1
kind: ConfigMap
metadata:
  name: sftp-public-keys
data:
  # both keys listed in single file
  keys.txt: |
    ssh-rsa AAAAB3Nz...3u8D
    ssh-rsa AAAAB3Nz...JQ0pz