In any case you will need some sort of server process running on the Windows box. For security reasons, you will want to strictly control what commands/programs can be executed on the windows system, and what information can be passed to them.

If you use ssh, you'll want to create a special user who hase very, very strictly limited access. Really any server process should run at a low level of permission, but with ssh we are granting the ability to remotely execute arbitrary commands and so the need for limits is particularly great.

Another approach would be to run apache (or another httpd) on the win-box, and write some perl CGI wrappers that do some policing of incoming data before executing the commands. You could even replace apache and run your perl scripts as daemons/services and connect directly to them.

I lean strongly toward letting apache handle your windows server needs and using CGI scripts to filter your parameters--your UNIX server can access the CGIs in relative safety. This way you aren't adding any new technologies to the soup, which should ease the maintenance burden. You also benefit because there are well known techniques for securing apache.


TGI says moo

In reply to Re: Running Windows executable on unix by TGI
in thread Running Windows executable on unix by sara2005

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.