The SSH daemon we're using now (kpym) does not support authorized_keys or scp, two major features of an SSH daemon required for automation. <catlee-buildduty> it had to work on the ancient talos boxes <catlee-buildduty> maybe that's not an issue any more We should investigate other options. I suggest looking at CopSSH which was easy to install and configure and has the features we need.
Armen is looking at deploying CopSSH with the new w64/win8 platform.
Not working on this at the moment.
I installed BitVise (http://www.bitvise.com/) at home on Windows 8 and confirmed that it supports public key authentication and scp. I don't know what licenses cost.
Armen: correct me if I'm wrong, but I thought we were sticking with KpyM because Q could actually make it behave the way we want, i.e. working scp and using authorized_keys?
This is old. Our current ssh/scp setup works.
Our current SSH daemon still does not support: - scp - multi-channel SSH sessions (for better automation) - having trouble getting passwordless logins and passwords working at the same time Q has also mentioned that he'd like to upgrade our SSH daemon to something better. I think we should keep this bug on file.
Should we move it to Relops?
Q, would you or markco like to take this on?
Something that supports "exec" would be nice.
Do we still care about this?