Postico 2.0 SSH Private Key Handling

In Postico 2.0, we've added a new feature where you can store the config directory in iCloud or Dropbox to sync server settings across Macs.

This feature is still incomplete, since we currently do not sync passwords or SSH private keys. I'm currently working on adding password syncing (encrypted with a master password). However, I'm not sure that we should also sync private keys.

Since I'm currently working on this feature, I'd like to get some user feedback. I see two possibilities:

1) When you add a SSH private key to a favorite, Postico should create an (encrypted) copy of the file and store it in the configuration folder, so that the private key syncs together with all other settings.

2) Move the private key setting somewhere else (eg. to preferences). Then you would need to configure SSH private keys on every device, and they would not be synced.

In my opinion, approach (1) would make it easier to use SSH keys when you have less tech savvy members on your team, while (2) is more useful if everyone already has their personal SSH keys, and you don't want people to share SSH keys.

Both approaches have their pros and cons, and I'm curious which approach would work better for you.

No file, test, or entry point is named. Start by reviewing the two proposed approaches for SSH private keys alongside the planned encrypted password syncing, then gather the requested user feedback. Done would be a documented decision about whether keys should sync in the configuration folder or be configured separately on each device.

Written by the indexing model from the issue text.