Suggestions for config path and password security

[No-22-Github]

Hi there,
I've been using sshw recently and really like how simple it is. I'm currently putting together an AUR package for it on Arch Linux, but I ran into a couple of things:

1. Config Path: It seems the app defaults to looking for .sshw.yml in the same directory as the binary (like /usr/bin). This doesn't really work on Linux without root. It would be much better if it prioritized ~/.sshw.yml or followed the XDG spec.
2. Security: Storing passwords in plain text is a bit risky. Have you thought about adding some basic encryption?

If you're busy, I'm down to submit a PR to fix the config path logic. Let me know what you think!

[lixvbnet]

Yes, sure, PR is always welcome!

1. For config path, it is already the correct order. It looks for config file first in user home dir and then bin_dir ( See config.go ). (unless os.UserHomeDir() is not working as expected in ArchLinux)

2. sshw is designed to be simple. Encrypting passwords would require a "Master password" on every login. But here's my personal advice in terms of security concerns:

Storing plaintext password is intended to be used for managing a bunch of pipeline machines which are constantly reinstalled but have a set of default passwords. Other than that scenario, you should instead generate an SSH keypair and upload the public key to remote server. sshw will load your private key at ~/.ssh/id_rsa .

Again, if os.UserHomeDir() has a different behavior in ArchLinux, please feel free to raise a PR.