The title says it all: the ability to have multiple SSH keys being able to push data into a CDN zone is a must for security and ease of use. As it currently stands, KeyCDN only supports one SSH key at a time per account.
Reasons why you’d want multiple SSH keys to be able to access your CDN:
- You have more than one device or location that you want to push data from (eg laptop, desktop, home/work, server etc)
- Sharing one SSH key between devices is a bad plan, and sharing keys between people is worse.
- In a team environment (or really, any environment with 2+ people), more than one person is going to need to push or modify data on the CDN. (see also Bus Factor)
- Sharing a username and password pair between people is also a bad plan.
- Passwords are inherently less secure than keys.
- Using FTPS clients whilst the server supports plain FTP means there’s a good chance someone will accidentally use FTP and send the password in the clear.
- Granting and revoking permission via multiple keys is far, far simpler than sharing credentials and needing to revoke/change them if key/password is compromised (or person leaves team)
There’s a very good reason platforms like GitHub, GitLab and Bitbucket all support multiple SSH keys for pushing code, and KeyCDN should too. Assuming the KeyCDN infrastructure is just passing the authorised keys from the web interface to something like
.ssh/authorized_keys, adding the ability to use multiple SSH keys should be fairly straightforward.
So, please implement this feature!
For note, yes, I know I could set a shared server up on my side, creating a common keypair that people share, and having people push from that machine, but this is a cumbersome workaround that requires also sharing a password (eg passphrase to key), and the key is still a shared credential. See all my above points about shared credentials being a bad idea.