That is the solution we've used at work in the past: ssh/scp
with passwordless access using public authorized_keys.
The part we don't like about this arrangement is, setting
up and breaking down the ssh pipes takes a longer
than we'd prefer, especially when doing a lot of little
operations in succession.
Ideally, we'd like to implement an RPC library which
builds (and re-builds if it is broken) an ssh pipe, and then
uses it persistently over multiple RPC requests.
Of course, most straightforward ways of doing this
bypass the security provided by ssh.
We looked into the perl RPC modules available about a year
ago or more, and the best we found was a module that used
shared secrets instead of public key encryption, which we
didn't like (and couldn't get to work). I'd think this
was a pretty common problem; I'm
surprised someone hasn't already figured out a more clever
solution that I can come up with, and put it into a module...
Alan
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.