This is immaterial to the "use keys" suggestion. I realize that you mentioned the key+password case, but I can't help but think that the solution to that is simply to go with a key without a password, limit the account on the other end as much as possible and swallow the bitter pill that if they have access to your passwordless private key, they probably have access to far more dangerous things.
In short, this can be solved with proper access restrictions and full key-based authentication, and nothing but bash and scp/sftp.
It could be, if the people running the other server were rational. In this case, it was faster to make it work than to have the meetings required to do a variance to their standards and to argue till I was blue in the tongue and still have them say no.
Comments
This is immaterial to the "use keys" suggestion. I realize that you mentioned the key+password case, but I can't help but think that the solution to that is simply to go with a key without a password, limit the account on the other end as much as possible and swallow the bitter pill that if they have access to your passwordless private key, they probably have access to far more dangerous things.
In short, this can be solved with proper access restrictions and full key-based authentication, and nothing but bash and scp/sftp.
It could be, if the people running the other server were rational. In this case, it was faster to make it work than to have the meetings required to do a variance to their standards and to argue till I was blue in the tongue and still have them say no.