CGI is a connectionless protocol. SSH is NOT.

In my opinion, you'd have to create a separate process to keep the ssh connection open, then connect to it from the CGI each time the CGI is called with new information from the web client.

Naturally, you'll have to count with the possibility of having more than one ssh connection open at the same time, so you'll have to have a way to connect to correct ssh "connector".

I strongly suggest you use CGI::Session to keep the identifying value only on your server, and NOT visible to the user - if the user can see it, they can usualy change it, and that would be a big security risk.

For some ideas on how to communicate between the CGI and the SSH connector, read perlipc

In reply to Re: Perl CGI SSH by matija
in thread Perl CGI SSH by The_Jesus

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.